Foglight® Agent Manager 5.9.2
Released with Foglight Management Server 5.9.2
Welcome to Foglight
New in this release
Resolved issues and enhancements
Third party known issues
Upgrade and compatibility
Getting started with the Foglight Agent Manager
Foglight® solution simplifies application performance
monitoring and reduces the skills and effort required to manage applications,
the user experience, and the supporting infrastructure.
Unlike other solutions, Foglight uses a single code base, and has a model-driven design that couples fast deployment and accelerated time-to-value. It offers the modular flexibility required to deliver a range of capabilities and sophistication to meet the needs of any organization—from those still focused on technology-centric monitoring to those that have completed the transition to application-centric or transactional monitoring.
Foglight performs equally well in physical, virtual, and mixed infrastructure environments, providing visibility into issues affecting the application and end-user experience. Intuitive workflows help you quickly move from the symptom to the root cause in the application, database, infrastructure, or network to resolve issues, reducing mean time to resolution. Predefined and drag-and-drop dashboards provide insight that is tailored to each stakeholder. By offering comprehensive visibility into your monitored environment, Foglight helps ensure that cross-functional teams collaborate on and prioritize issues that matter most to the business.
Foglight agents require the Foglight Agent Manager (FglAM) to manage their life-cycles and centralize communications with the Foglight Management Server.
For information about the supported platforms for the Agent Manager, see the System Requirements and Platform Support Guide.
These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.9.2 release of the Agent Manager. Review all sections before starting the installation.
This release of the Foglight Agent Manager contains the following new features:
Release Notes for the Agent Manager Development Kit are now provided in a separate document: Foglight Agent Manager 5.9.2 Development Kit Release Notes.
The following is a list of issues addressed and enhancements implemented in this Foglight Agent Manager release.
|FAM-7254||Agent in ext FglAM did not collect data without any error logs after the Agent Manager started for a few hours.|
|FAM-7241||"Too many open files" error was reported by many FglAMs running on Solaris.|
|FAM-7239||Fixed issue where FglAM picked up IPv6 address as the host name.|
|FAM-7214||Fixed issue where some FglAM commands caused FglAM crash.|
|FAM-7207||The Agent Manager dashboard loads slowly when loading more than 800 FglAMs.|
|FAM-7177||Unexpected NullPointerException results in broken agents.|
|FAM-7175||Fixed issue where some FglAMs incorrectly shown as not upgradable.|
|FAM-7173||Supported "diffie-hellman-group-exchange-sha256" in SSH connection.|
|FAM-7145||Support more MAC algorithms, including hmac-sha2-512, hmac-sha2-256, and hmac-ripemd160.|
|FAM-7134||Inconsistent agentPackage version results in broken peers.|
|FAM-7086||Output of "fglam --status" does not match what is documented.|
|FAM-7079||Fixed issue where the file log scanner stopped scanning logs.|
|FAM-6996||Fixed the "Too many open files" error occurred when stopping and starting data collection for the JMX agent.|
System Lockbox failure may happen when moving agents.
Foglight Agent Manager generated a NumberFormatException exception while executing activity of WindowsEventLog.
|FAM-6930||Fixed issue where the Agent Manager encounters a "Permission denied" error when user attempts to upgrade the jre file.|
The following is a list of issues known to exist at the time of this release.
|FAM-7210||The Agent Manager version number is incorrect on the Script Console dashboard, after being upgraded to 126.96.36.199.2 from 188.8.131.52.1.|
|FAM-7209||FglAM-Adapter-Devkit-6.1.3 is missing after the Agent Manager is upgraded from 184.108.40.206.1 to 220.127.116.11.2.|
FglAM running on Linux/Solaris fails to connect to the target host
through link-local IPv6 WMI, if multiple network interfaces exist in
the target host.
1. Log into the target host.
2. Execute the dos command->ipconfig/all command, to check how many tunnel interfaces which contain IPv6 address.
3. If only Tunnel adapter Teredo Tunneling Pseudo-Interface and Ethernet adapter Local Area Connection exist in the target host, uninstall/disable Teredo Tunneling Pseudo-Interface, and then check if the WMI connection can be established.
|FAM-7183||Adapter should alert upon FglAM failover and when cluster members are in the BROKEN state.|
|FAM-7169||WinRMCommandShell returns empty output when using BAT scripts.|
WMI connection cannot be established successfully when using the
IPv6 address to monitor the target host.
1. Set the agent's target host address and credential resource mapping to the long form, for example: fc00:0:0:0:0:0:a1e:9804.
2. Check if the WMI connection can be established. If not, change the agent's target host address from long form to compressed form (fc00::a1e:9804). If this solution still does not work, check the workaround in FAM-7193.
|FAM-7072||Installer fails to exit and FglAM cannot report to FMS.|
|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.|
Cannot deploy multiple HA-aware gars to a standby host at one time.
HA failover fails and the value of mState on standby peers changes to
Workaround: If the failure of HA failover is caused by MISSING_LOCKBOX (Check the HA partitions info by navigating to JMX console > HAManager > diagnosticSnapshotAsString()), perform either of the following options to resolve this issue:
1. On the navigation panel, under Dashboards, click Administration > Credentials > Manage Lockboxes. In the Manage Lockboxes dashboard, release the missed lockboxes to the MISSING_LOCKBOX FglAM client. If you cannot find the missed lockboxes, perform step 2.
2. On the FglAM client that has the MISSING_LOCKBOX status, navigate to <fglam_home>\state\<state_name>\credentials. Clean up all files under this directory, and then restart the FglAM. After the restart completes, release all lockboxes as Primary in the Administration > Credentials > Manage Lockboxes dashboard.
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 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.
Agent is not listed under "agents" property of FglAMClientInstance or Host object after moved.
The Agent Manager fails to connect to the Management Server while using the default HTTPS SSL certificate.
Workaround: Install a newer certificate on the Management Server.
|FAM-6688||Support is required for installing and running Agent Manager on a system with SELinux enabled.|
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.
The Agent Manager fails to start up after an upgrade.
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.
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.
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.
OutOfMemoryError: The Agent Manager cannot create new native thread. It shuts
down when the open file descriptor limit is too low.
The Agent Manager running on Solaris may fail to run local or external commands during startup or through the SSHLocalConnectionImpl class.
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" )
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.
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.
This release of the Foglight Agent Manager does not include any third party known issues.
The 5.9.2 Foglight Agent Manager cartridge requires Foglight Management Server 18.104.22.168 or later. The cartridge is compatible with all previously released versions of the Agent Manager client application.
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 5.9.2 Agent Manager cartridge or upgrading the Foglight Management Server to version 22.214.171.124 or later. After all of the legacy hosts are running version 5.6.7, and the Foglight Management Server is upgraded to version 126.96.36.199 or later, you can start upgrading your hosts to version 5.9.2.
The following is a list of Foglight product versions and platforms compatible with this release.
|Foglight Management Server||188.8.131.52 and later||All platforms supported by these versions of the Foglight Management Server|
|Foglight Agent Manager Development Kit||5.9.2||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.
The following operating system is not supported as of version 5.8.5:
Support for the following operating systems will be discontinued in an upcoming Foglight release. This platform is supported in this release. We hope this notice of planned support changes helps you plan your upgrades.
For detailed information about system requirements, see the System Requirements and Platform Support Guide.
Foglight includes a licensing capability that restricts access to those features that are defined in the license. All Management Server installations require a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight for Infrastructure), others may require an additional license. Foglight Agent Manager is covered by the base Foglight license.
To activate a trial or a purchased commercial license:
Foglight Agent Manager 5.9.2 is distributed with Foglight Management Server 5.9.2.
For information about what is included in the Foglight 5.9.2 release package, see the Foglight Release Notes.
Refer to the Foglight Agent Manager Guide for installation and configuration instructions.
Additional information is available from the following:
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
This release has the following known capabilities or limitations: The Management Server and Agent Manager client will be enabled for Global Operations, but not localized to any particular locale. Legacy Foglight 4 agents will continue to be limited to the locales supported under Foglight 4. Consult the Global Operations statement for each agent to determine its own capabilities and limitations. The Agent Manager currently requires installation in a directory path with only ASCII characters.
We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.
Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.
For sales or other inquiries, visit www.quest.com/contact.
Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:
Quest, the Quest logo, Foglight, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.