Welcome to Foglight
Resolved issues and enhancements
Third party known issues
Upgrade and compatibility
Getting started with Foglight
Quest's 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.
These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.9.3 release of Foglight. Review all sections before starting the installation.
Note: Foglight will be discontinuing support for the following operating systems starting with the next Foglight release: 32-bit Windows, 32-bit Linux, Solaris SPARC64, and Solaris 86-64. If you are still using these platforms and need further assistance, contact Quest Support.
The 5.9.3 release of the Foglight Management Server contains the following new features and enhancements:
Foglight Command Line
Topology Objects, Notifications, and Registry Variables
Third party libraries
Foglight Agent Manager
The Foglight Agent Manager (FglAM) was upgraded to version 5.9.3. For more information about the Foglight Agent Manager 5.9.3, refer to the Foglight Agent Manager 5.9.3 Release Notes.
The Infrastructure cartridge was upgraded to version 5.9.3. For more information about the Foglight for Infrastructure 5.9.3, refer to the Foglight for Infrastructure 5.9.3 Release Notes.
The following is a list of issues addressed and enhancements implemented in this release. For a list of resolved issues for the Foglight Agent Manager and the Infrastructure cartridge at the time of the Foglight 5.9.3 release, see the Foglight Agent Manager 5.9.3 Release Notes and Foglight for Infrastructure 5.9.3 Release Notes.
Fixed issue where the Database dashboard occasionally displays a blank page.
Some cartridges were not enabled when the Foglight Management Server starts the first time, without installing any license.
On the Alarm Filter dialog box, the "Alarm filter criteria is too broad" error prompts when using the filter of agent type with "DB_SQL_Server".
Fixed issue where IP/Host binding does not work anymore in the Management Server 5.9.2.
Fixed vulnerabilities on the following CVEs:
Fixed issue where the embedded the configuration file baseline.jvmargs.config was overwritten during upgrade to the Management Server 5.9.2.
|Fixed issue where the number of idle connections was used as AvailableConnectionCount.
Fixed issue where the agent's tag definition did not work.
When deleting an agent from one blackout, the other blackouts of this agent will be removed as well.
The following is a list of issues known to exist at the time of this release.
Note: Check the release notes for each cartridge you will be using for known and late-breaking issues with that cartridge.
For a list of known issues for Foglight Agent Manager in this release, see the Foglight Agent Manager 5.9.3 Release Notes.
Foglight for Automation is not supported:
See below for details. These limitations will be addressed in a future release.
When a Foglight Management Server running in High Availability mode fails over, all in-progress tasks fail and the system cannot recover them.
The Foglight Cartridge for Automation should not be installed, and workflow automation must not be used, on a Foglight Federation Master. This is because active tasks that update topology objects are not permitted on the Federation Master. Workflow automation may be installed and used on the Federated Child(ren) as usual.
Custom rules (which are copied from existing cartridge rules) will drop some tables or charts that exist in the original Alarm dialog. Contact Quest Support for workaround.
The upgrade to version 5.9.3 completes successfully but the installation log contains shorcut creation failures.
The Management Server UI will possibly be displayed abnormally if Tomcat version is upgraded.
Workaround: Clear the cache data of your web browser.
If you toggled enable/disable state for Alarm Integration, Incident Integration, Clear Integration Alarm, or QMX Agent Host Connection Rule rule in the Integration cartridge, its enable/disable state will be reset after upgrading to 5.9.x from 126.96.36.199.
When upgrading the Management Server from 188.8.131.52 to 5.9.x, unexpected CartridgeDeploymentException shows in the log file.
Workaround: This exception only occurs in environments with those cartridges which define Java Archive or JBoss Artifacts component, like Integration and IntelliProfile cartridges. JBoss Server has been removed from the Management Server 5.9.x. As a result, JBossDeploymentHandler, which was used to handle above components, has also been removed from the Management Server 5.9.2 or later. If you encounter this issue, you could ignore it as this exception does not impact upgrade of the Management Server and relevant cartridges.
After first installing this version of the Foglight Management Server,
EU appliances may fail to connect with the Foglight Management Server.
Workaround: Restart the Foglight Management Server after the installation.
|LDAP accounts may fail to bind to the OU group whose name includes backslash characters '\'. This can prevent Foglight to authenticate LDAP users.
|FSMService availability calculations do not work as expected in a service hierarchy.
FoglightShutdownAction.checkInUsedPort() does not load port settings from server.config during an upgrade.
In a Windows Single-Sign ON (SSO) with untrusted multiple domains, only the user with the keytab file-corresponding group can be imported.
The Management Server data-driven multiple severity rules may fire multiple times for the same severity in case of concurrent data submissions.
The rule engine may pass non-persisted alarm IDs to rule actions. This can prevent some alarms, that are generated multiple times against the same scoping object, from firing.
|PostgreSQL fails to start up while installing the Management Server with an embedded PostgreSQL database on a Korean OS.
Failing to start the Management Server with the --host=*.*.*.* option due to a failed attempt to start the embedded database.
LDAP users may have to log in twice to get proper role assignments.
Foglight is configured with a list of default ciphers. Some of these ciphers are potentially vulnerable ciphers. A review of the ciphers that will be available in a future release is ongoing.
Workaround: Edit the list of ciphers by completing the following steps:
For complete information, visit
The Management Server distribution layout contains some confusing directories under server/jboss.
|ObservationQueryPlan$QueryStep.getDayIndex(...) can result in ArrayIndexOutOfBoundsExceptions during a Daylight Savings Time (DST) change.
Core monitoring policy derivations are not deployed on a Federated Master.
Excluded objects are sometimes included in a Federation topology synchronization.
A Foglight Agent Manager that is no longer in use maintains a stale disconnected RemoteObject instance under the host object. This causes the host to appear as undefined on the Hosts dashboard, even though the host is monitored by Foglight for Infrastructure.
When federation.config does not contain any queries, TopologySynchService mistakenly logs the following warning:
WARN Obsolete federated topology object purge will not be performed because the following federated servers are not connected: ...
Topology loading can fail for topology objects that have been converted to DataObjects.
Type-based exclusions in federation.config do not apply to referenced objects.
String observations containing reserved characters in script agents are not supported.
The alarm email notification code does not persist any information about notification alarms that were previously sent. If the server is restarted, all alarms appear as new, and the notifications are resent.
Hibernate/JDBC errors occurring while loading rules return an empty list.
Cleared credential alarms are found when querying for alarms that are not cleared.
Simple rules that report alarms directly are not affected by blackouts.
|Diagnose link doesn't work on the Master FMS
An attempt to import external groups results in the following error:
Could not execute the requested operation, error(s) had occurred: Failed to retrieve groups, please make sure you correctly configured the Directory Services, check log for details.
The log, however, does not contain any errors.
After changing the value of the registry value, some of the performance
calendars may disappear from the list.
When editing properties from the Agent Status dashboard or the Agent
Properties dashboard in Chrome 17, some edit fields are not available.
The Cartridge Inventory page is currently unable to alert users if a cartridge install fails due to lack of space in the server's temp directory. An error is written to the log files.
When editing secondary agent property tables from either the Agent
Status or Agent Properties dashboards, performing Add and Delete
operations at the same time results in all Added items being deleted.
Selecting the time range "All" on the Service Details dashboard can result in the page getting stuck refreshing. Avoid using the "All" time range on this page.
Selections made on the Service Selector tab of the Select services and tiers to monitor dialog box of the SOC become unselected when you switch to the Tier Selector tab and back again.
The first time the Environment Report is run it may generate a warning:
- Text ... did not fit. in view ..."
Credential alarm messages sometimes contain UUIDs for objects related to
When using a Federation Master that is a newer version than the Federated Child, it is possible to get warnings about missing metrics. This occurs when new metrics have been added to the Federation Master's version. The warnings indicate that the Federated Child does not provide these metrics, and they will cease when the Federated Child is upgraded to the same version as the Federation Master.
When editing secondary agent property lists, the Delete Selected Row(s) button marks the rows to be deleted by graying them out. Save changes must be selected to delete the selected rows. If a required field is blank, then a value must be entered before the row can be marked for deletion.
In the Service Builder and Service Operation Console (SOC) dashboards, when alarm filters are configured, they are applied to the main dashboards (Service Builder and SOC dashboards) and to some first level popups only. The alarm filters are not applied throughout all popups/drilldowns at any level.
When reviewing Alarms on a Federation Master, you are able to open a link to view the rule that fired the alarm on the Federated Child. This involves opening the console of the Federated Child. If the Federated Child is of an older version than the Federation Master, an error page is displayed.
Under rare conditions, if the session is allowed to expire while viewing some of the views in the Administration dashboard, the process of logging in again displays the Administration view without any decoration around the side panels.
Workaround: To clear this condition, close the browser. Do not save your session if the browser prompts you to save the last session configuration. Instead, start the browser and log in again.
The column layout on the Agent Status Page does not allow resizing of columns, which can result in the host name appearing truncated.
An error message stating "Error getting value of context entry with key:timeRange" can appear in the logs when using the popup menu on the Origin field of the Alarm Details dialog.
If a Federation Master Server connects to an older version Federated
Child, the Federated Child may have some of the objects that are no
longer associated with the Management Server Performance Report and
Foglight Server Diagnostic views on the Federation Master. This results
in some data about the Federated Child being unavailable to this report
Inconsistency in the number of alerts shown in the "All Alarms Chart" and "Alarm List with Filter" in the Alarms dashboard.
Display all available scoping objects in the condition editor for copied and user-created rules.
On systems with a large numbers of hosts, the Host Table view can be slow to display.
Foglight 4 Tabular views generate an error when the time range has "Auto" granularity.
The edit rule definition for an alarm from a Federated Child brings up a page for editing a rule on the Federation Master, rather than for the rule that triggered the alarm. This occurs because it is not possible to perform administration from the Federation Master.
When the user pastes data using right-click > Paste to
a box that automatically updates itself (for example, the edit agent
properties screen), the user interface does not automatically refresh
When agent activation fails, the "Activating" status box does not show the status of the failed start agent.
The Service Levels Details page does not show cleared alarms for Service Level Policy.
Seconds should be displayed in the startTime and endTime in the WCF under Browse > Data when granularity is set to "raw".
QP5 needs to be upgraded to the latest version.
In Internet Explorer 8, when the number of dashboard nodes in the navigation panel exceeds the maximum that can be displayed without a scrollbar, the scrollbar does not immediately appear.
Tree Table list nodes should not be clickable or dwellable.
PDF charts and files that were requested through a proxy fail and result in a Connection Refused error. Note that this error only applies to requests made by the Management Server.
Vertical scrollbar not shown for the text area.
The following is a list of third party issues known to exist at the time of this release. For a list of third party issues related to the Foglight Agent Manager at the time of the Foglight 5.9.3 release, see the Foglight Agent Manager 5.9.3 Release Notes.
The Foglight Management Server generates an "Unable to load Java VM shared library to start JVM" message when attempting to start the Management Server on a Red Hat Enterprise Linux Server 5.0 VMware machine.
This is caused by the SELinux security code on newer RedHat systems. There are two workarounds:
This issue is addressed in the Sun JDK 1.6.0 release notes:
Console Mode. Returning to a previous step in the installation process
after being prompted for a user password, the input is not recognized.
Installation: Console Mode. Some characters of the Administrator's password
are not hidden if typed too quickly.
When typing words containing "ss" in the online help search, a
null pointer exception is generated.
See the Foglight 5.9.x Upgrade Guide for information about upgrading Foglight and for a list of the latest cartridge versions that are compatible with Foglight Management Server 5.9.3.
For information about system requirements for this release, see the Foglight 5.9.x System Requirements and Platform Support Guide.
The following operating systems are not supported in this release:
Support for the following operating systems will be discontinued in upcoming Foglight® release. We hope this notice of planned support changes helps you plan your upgrades.
Support for Microsoft® Internet Explorer® 8, 9, and 10 is discontinued as of this Foglight® release.
Microsoft ended the support for these versions on January 12, 2016. For more information, visit https://support.microsoft.com/en-us/lifecycle?p1=13418.
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 Agent Manager cartridges and the Cartridge for Infrastructure), others may require an additional license.
To activate a trial or a purchased commercial license:
The Foglight 5.9.3 release package contains the following:
See the Foglight 5.9.x Installation and Setup Guide set for installation 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 server will be enabled for Global Operations, but not localized to any particular locale. Some legacy agents cannot support multi-byte locales.
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 http://quest.com/company/contact-us.aspx.
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.