Version 7.1 of Foglight contains the following new features and updates:
Security Enhancements
Updated Java JRE used by Foglight to version 17.0.8
Updated third-party libraries
Add the ability to remove literals from queries collected. Supported for selected database cartridges. Check relevant release notes.
Foglight Agent Manager Enhancements
FglAM HA partitions will now automatically fail back to the highest priority FglAM
User Experience Enhancements
Revised the header across all foglight dashboards to include new breadcrumbs, timeframe selector, and reports
Open source and No-SQL database menus are now conveniently located under the “Databases†menu on the left for easy navigation
Change the location of the “Pin†button for the left navigation bar
Improve Query Insight layout to allow change of width between the two parts of the screen
The following is a list of issues known to exist at the time of this release.
Defect ID |
Known Issue |
FGL-20503 |
Fail to download the FglAM installer via server download page. |
FAM-7697 |
The connection test via installation GUI or headless would take about 2 minutes when FglAM and FMS are in different FIPS modes. |
FAM-7559 |
Agents fail to monitor the WinServer2019 Domain Controller via DCOMWindowsCommandShell connection. |
FAM-7365 |
The Infrastructure agent fails to collect the data due to the "Failed setting a value for obsolete node:" error. |
FAM-7342 |
Part of data collected on the Host dashboard is missing due to ConnectionBrokenException. |
FAM-7341 |
The CPU usage of the Agent Manager constantly reaches 100%. |
FAM-7330 |
The "sqlserv.exe process" and "Memory Top Consumers" metrics collected by the Windows Agent are incorrect. |
FAM-7307 |
Many errors show in the Agent Manger log and there is no data displayed on the VMware dashboard. |
FAM-7210 |
The Agent Manager version number is incorrect on the Script Console dashboard, after being upgraded to 5.8.5.5.2 from 5.8.5.5.1. |
FAM-7209 |
FglAM-Adapter-Devkit-7.1.0 is missing after the Agent Manager is upgraded from 5.8.5.4.1 to 5.8.5.4.2. |
FAM-7169 |
WinRMCommandShell returns empty output when using BAT scripts. |
FAM-7116 |
WMI connection cannot be established successfully when using the IPv6 address to monitor the target host. |
FAM-7023 |
Agents will be broken (FMS deletes them), after changing FglAM host name, IP, or display name. The agents will be recreated when the FglAM starts with the original FglAM display name. |
FAM-6998 |
Cannot deploy multiple HA-aware gars to a standby host at one time.
|
FAM-6942 |
HA failover fails and the value of mState on standby peers changes to MISSING_LOCKBOX in JMX console. |
FAM-6940 |
There are duplicate IP addresses for different FglAM instances (running on Linux) in the Agent Managers dashboard, if the FglAM servers are cloned virtual machines.
Workaround 2:
Workaround 3: If you have cloned the servers, do not start up the FglAM. Set system.id.enabled = false for all FglAM instances in the <fglam_home>/state/<state_name>/config/client.config file, and then start the FglAM for the first time. |
FAM-6934 |
Agent is not listed under "agents" property of FglAMClientInstance or Host object after moved. |
FAM-6688 |
Support is required for installing and running Agent Manager on a system with SELinux enabled. |
FAM-6439 |
Upgrades from 5.7.4 to 5.8.1 or 5.8.2 may result in an error during the upgrade process. Workaround: If you are currently running a 5.7.4 install and you want to upgrade, then you must upgrade to version 5.8.5 or later. |
FAM-5854 |
Foglight Log Monitor does not support UNC (Universal Naming Convention) paths. Workaround: The following workaround applies when monitoring local log files. Monitoring remote log files is not supported.
|
FAM-5832 |
Installing and configuring multiple Foglight Agent Manager instances on a single physical host can cause some topology churn in the Host model representing the Agent Manager. Workaround: By default, the Agent Manager submits performance metrics about itself. If multiple Agent Manager instances are running on the same physical host, disable the performance monitoring self-metric submission for each Agent Manager Instance by completing the following steps:
Additionally, an Agent that submits a Host object representing the monitoring host (for example, an Agent Manager instance that is running and hosting an agent instance) as part of its monitored collection causes a Host topology churn when these agent types are deployed to additional Agent Manager instances running on the same physical host. |
FAM-5600 |
The Agent Manager vm.config file migration fails under multi-state installs. Workaround: The legacy vm.config file is replaced with two new configuration files: client.config and baseline.jvmargs.config. Locate these files within the upgraded Agent Manager state instance. As these file instances may already contain transferred values from the legacy vm.config, review each of the settings in both of these files in order to ensure that these configuration options apply to the Agent Manager state instance that they are being copied into.
|
FAM-5355 |
OutOfMemoryError: The Agent Manager cannot create new native thread. It shuts down when the open file descriptor limit is too low. |
FAM-4955 |
Parentheses can cause a command execution to fail while using a LocalWindowsCommandShell connection. Workaround: If parentheses are used for grouping commands (and not in an echo context), use spaces to separate them from the other tokens in the command. For example, instead of this command: if 3 gtr 2 (echo "3>2") else (echo "3 leq 2") Use the following: if 3 gtr 2 ( echo "3>2" ) else ( echo "3 leq 2" ) |
FAM-2850 |
Slave processes exist for all installed out-of-process (OOP) agent packages, even if no agent instances are running. Workaround: OOP packages which are not running any agent instances may be un-deployed from the Agent Manager. Currently, this is only possible using a manual procedure. |
FAM-1972 |
The deployed agent scratch directory created for JFogbank-type agents is not deleted during an upgrade. Workaround: The orphaned directory is benign, and can be manually deleted after the upgrade is complete. |
The following is a list of third-party issues known to exist at the time of this release.
Defect ID |
Resolved Issue |
FOG-330 |
Get AccessControlException when executing HTTP requests in multi-thread tasks in the latest FglAM version. |
The 7.1.x Foglight Agent Manager cartridge requires Foglight Management Server 7.1 or later
Agent Manager upgrades from a 5.5.4.x legacy release require an intermediary upgrade to 5.6.7 prior to upgrading to 5.8.5 or later. To complete this intermediary upgrade, install one or more of the Agent Manager 5.6.7 platform-specific cartridges (as required), and upgrade the legacy hosts to this release before deploying the 7.1.x Agent Manager cartridge or upgrading the Foglight Management Server to version 5.9.2 or later. After all of the legacy hosts are running version 5.6.7, and the Foglight Management Server is upgraded to version 5.9.2 or later, you can start upgrading your hosts to version 7.1.x.
The following is a list of Foglight product versions and platforms compatible in this release.
Product Name |
Product Version |
Platform |
Foglight Management Server | 7.1.0 or later | All platforms supported by these versions of the Foglight Management Server |
Foglight Agent Manager Development Kit | 7.1.0 | All platforms supported by these versions of the Foglight Agent Manager Development Kit |
For more information about upgrading the Management Server and the Agent Manager, see the Foglight Upgrade Guide.
When upgrading external Agent Manager, if the new Agent Manager uses a higher version JRE than the old Agent Manager, the JRE trust store (cacerts) in the old Agent Manager will be replaced by the new trust store from the higher version JRE. This will cause all the custom certificates imported to the old JRE trust store by customers get lost after the Agent Manager upgrade.
To keep the custom certificates, you need to back up the old JRE trust store before upgrading external Agent Manager, by following below steps:
As for the embedded Agent Manager, it uses the same JRE as the Management Server. If there are custom certificates stored in JRE trust store and a higher JRE version is used, back up the JRE cacert trust store used by the Management Server before upgrading Management Server.
Note: if the new JRE trust store has different entries than the old JRE trust store, there is a risk that these entries would get lost after replacing with the old JRE trust store.
Below is a list of JRE versions used by Agent Manager on various platforms in this release:
Platform |
JRE Version |
windows-x86_64 |
17.0.8 |
linux-x86_64 |
17.0.8 |
Note: To avoid the need for reinstalling the certificate after an upgrade, it is recommended to install an FglAM CA certificate using the fglam- -add-certificate method instead of the keytool command. For more information, refer to the Configuring the Agent Manager to use SSL certificates section of the Foglight Agent Manager Guide.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center