The following is a list of issues addressed and enhancements implemented in this release.
Defect ID |
Resolved Issue |
FAPM-1945 | Updated to include the Enduser-Models_5_9_11.car cartridge file. |
FAPM-1701 | Fixed issue where Application-Root-Base.car could not be enabled on the Foglight Management Server 5.9.x. |
The following is a list of issues resolved in hotfixes issued for the previous release. These issues are also fixed in this release.
Defect ID |
Resolved Issue |
FAPM-1646 | Foglight for Application Operations has been rebranded to Quest Software Inc. |
FAPM-1641 | Remove the dependency with Foglight for Infrastructure cartridge, as Infrastructure has been a part of the FMS since release 5.6.4. |
FAPM-1455 | Nodes under All Services show blank after performing a search. |
Defect ID |
Resolved Issue |
FAPM-1103 | The NullPointerException is thrown when invoking the DataAggregation.java class. |
FAPM-1099 | Update the help documents to remove the SaaS related contents. |
FAPM-1090 | Remove the obsoleted v5 and v6 integration codes from build-main.xml, ivy.xml, and build.external.properties. |
FAPM-906 | The integration cartridge (Dependency-Oracle-Integration) now requires Oracle 5.7.5.1 or later to work. Note: DB_Oracle 5.7.5.1 or later is required to ensure that the Dependency-Oracle-Integration cartridge can work in your environment. If you are using the older version of DB_Oracle, it is strongly recommended that you upgrade DB_Oracle to version 5.7.5.1 before installing the latest Foglight for Application Operations 5.9.8.3 package; otherwise the previously installed Dependency-Oracle-Integration cartridge will be disabled after the installation, and you need re-enable the integration cartridge manually. |
Defect ID |
Resolved Issue |
APM-8693 |
On the APM > Transactions dashboard, |
APM-8688 |
Related to APM-8686. On the APM > Transactions dashboard, the tiles do not update when the registry variable is |
For custom application transactions (Java EE and .NET) only. A summary transaction tile for an application in the dependency mapping view is created when the registry variable is |
Defect ID |
Resolved Issue |
APM-8664 |
Duplicate transactions were found in the Application Operations dashboards. Fix: Custom application transactions cannot be created if the |
APM-8547 |
Data did not display on the Transaction > Response Time Breakdown tab. |
APM-7964 |
The host and application were displayed in the APM > Transaction > Response Time Breakdown Explorer, but were displayed on the Application Infrastructure tab. |
APM-7963 |
There is a typo on the APM > Transactions view. The word "on" is replaced by "no" in the message: "There are no Application Components for this item." |
The following is a list of features deprecated in Foglight for Application Operations version 5.9.8.2:
The following is a list of issues known to exist at the time of this release.
Defect ID |
Known Issue |
FAPM-2079 |
Unexpected Custom Metrics tab shows in the Transactions dashboard, as Foglight APM for Real User Experience 5.9.x is not compatible with the Management Server 5.9.1. |
FAPM-2008 |
In the Federation Master Server, the status icon on the Sequence Explorer dashboard is not synchronized from Federation Child. |
AGENT-2530 |
The Netstat agent does not support monitoring dependencies for a network in which there are private networks. The Netstat agent may report wrong dependencies because it is unable to distinguish whether a host is private host, and to which private network a private host belongs. Workaround: To avoid reporting incorrect dependencies, add all private IPs to either the "Excluded Hosts List" or the "Global Excluded Hosts List" secondary ASP. This prevents the agent from attempting to get a netstat result from them. Note: A consequence of this workaround is that no dependency information is reported for all private hosts. |
APM-3485 |
On the Transactions dashboard, it may be unclear to users that ungrouped transactions are not part of the last grouped transaction. Ungrouped transactions are not indented (that is, the first tile appears closer to the left edge of the dashboard than the grouped transactions). |
APM-3375 |
On the Transactions dashboard, transaction groups with the same severity may not be sorted alphabetically. In addition, tiles under a specific pivot group may not render in the same alphabetical order. |
APM-2051 |
In systems where several credentials are available for accessing a host for monitoring, the connection to the target host is established successfully using one of the defined credentials, but the system generates the following warning message due to the other credentials defined for that host:
Workaround: To avoid this situation, ensure that the Windows credentials are not mapped to non-Windows host(s) in your system. |
The following issues are specific to Real User Experience, Java EE Technologies, and/or .NET transactions.
Defect ID |
Known Issue |
APM-3637 |
In the Sequence Explorer, in rare cases where there are few collections (or only one) in the time range, the |
APM-3532 |
In the Sequence Explorer, selecting a previous timeslice does not affect the threshold state on the exit values. |
APM-3425 |
Java-only transactions collected by the Foglight for Java EE Technologies agent version 5.8.2 do not report Exceptional exits. The number of Exceptional Exits on the Java Tile is always zero. |
APM-3417 |
The Error Explorer dashboard only shows exceptional exit data from Java EE and .NET agents of version 5.9.0 or later. Data from earlier agent versions does not appear on this dashboard. |
APM-2336 |
Tile and icon views are not supported in custom column-style dashboards. |
APM-2099 |
A Netstat agent starts collecting data immediately after the agent creation process is completed. In some cases, the Management Server walks the agent through unexpected state transitions, which places the agent into an unknown state, which in turn results in the agent missing the first data collection interval. |
The following issues are specific to FxM and FxV transactions.
Defect ID |
Known Issue |
APM-3551 |
For drag-and-drop dashboard creation: the |
APM-3550 |
The |
APM-3132 |
In rare instances, multiple FxV hit filters may source identical transactions in the same time period. |
APM-2883 |
There are some cases where a zero value for a location measurement is assigned a rank, for example when there are fewer than 100 values for the specific application component. In these cases, the rank is technically correct, but not meaningful and not necessarily consistent with other empty values which may go without a rank. |
APM-2871 |
If the FxM Appliance is at or near capacity, deploying the map agent aggressively may impact FxM performance and cause FxM to drop packets. |
APM-2824 |
The application data by location count does not always add up to the total application count. |
The following issues are related to upgrading from Foglight for Application Operations version 5.7.x.
Defect ID |
Known Issue |
APM-3572 |
An upgrade from version 5.7.1 to version 5.9.0 causes additional irrelevant Group By options to appear on the Response Time Breakdown dashboard. |
APM-3568 |
An upgrade from version 5.7.x to version 5.9.0 requires a manual update to the retention policy for the RequestTypes object.
|
APM-3564 |
After an upgrade from version 5.7.1 to 5.9.0, the Geographical Perspective views populated by Foglight APM for Real User Experience and Web may not allow drilling down for a specific location if the dialog was opened directly from another location detail view. |
APM-3539 |
If the Dependency_Mapping_Transitive_Child_Queries and/or the Dependency_Mapping_Child_Queries registry variables have been edited, upgrading to version 5.9.0 requires the following workaround to ensure that the changes are preserved in a way that is compatible with the new version.Workaround: Make a backup of the edited registry variables. Run the following script to update the registry variables so that they are compatible with the new version:
|
APM-3516 |
Upgrading from Foglight for Application Operations 5.7.1 to 5.9.0 may cause the Geographical Perspective dashboard to become inaccessible. |
APM-561 |
The configuration settings for agents created using an older version of the administrative UI cannot be edited in the Configuring Settings for <NetstatAgent_Name> dashboard. |
The latest version of Foglight for Application Operations is version 5.9.8.5. Upgrades from version 5.9.x, 5.7.x, and 5.6.4.x are supported.
Note: Only this version of Foglight for Application Operations supports the Management Server 5.9.1.
The following Foglight product versions and platforms are compatible with this release.
Product Name |
Product Version |
Platform |
Foglight Management Server | 5.7.5 and later | All platforms supported by this version of the Foglight Management Server |
Foglight Agent Manager Note: The monitoring agents available in this version of Foglight for Application Operations do not support the Agent Manager HA failover mode. For more information about this mode, see the Agent Manager Guide. |
5.8.5 and later | All platforms supported by this version of the Foglight Agent Manager |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center