Foglight agents require the Foglight Agent Manager (FglAM) to manage their life-cycles and centralize communications with the Foglight Management Server.
What’s new in this version
The following is a list of issues addressed and enhancements implemented in this release.
Agent Manager Core
FAM-6818 Validating memory settings from resource negotiation during an upgrade could result in mismatched -Xms -Xmx values.
FAM-6783 The Agent Manager failed on startup if the fglam-config.xml file contained invalid syntax.
FAM-6746 When the baseline.jvmargs.config was edited to allow for change in heap settings, the negotiated vm.deployment.config was not deleted, preventing the new baseline values from being applied to the Agent Manager runtime.
Fix: The change is now detected on startup, and the vm.deployment.config option is automatically deleted.
FAM-6729 The com.sun.xml code that requested a logger as an indirect result of an agent call triggered a security exception.
FAM-6548 Foglight Log Monitor agent could not determine the target Solaris x86_64 architecture, failing to monitor the target host log files.
FAM-6723 The IAgentTransferService prevented agents from being activated if a transfer is in progress during an Agent Manager negotiated restart.
FAM-6489 The system upgrade time-out property did not match the corresponding FglAM adapter property, resulting in an upgrade failure.
Remote Connections and Credentials
FAM-6833 If the SSL certificate used for the WinRM HTTPS required EC (Elliptic Curve) cryptography, EC caused a problem while verifying the certificate's signature.
Script Agent Support (JCollector)
FAM-6828 Merging a script agent's STDOUT and STDERR could break data submission.
COM-1509. FAM-6497 - During the installation of an Agent Manager on an AIX system, if the configuration option to start the Agent Manager process at the end of the install was selected, the installer could fail to launch the Agent Manager process on exit.