The following is a list of issues resolved and enhancements made in this release.
|
Defect ID |
Resolved Issue |
| APM-6746 | Added the option to view the Entire Period in the timeslice selector on the Geographical Perspective Dashboard. |
| APM-6701 | Improved the performance of the Transactions Dashboard. |
| APM-6654 | Updated the APM Transaction tiles to correct a display issue with locations. |
| APM-4900 | Fixed an issue that was causing the Management Server to consume 100% CPU. |
| APM-4243 | The Before and After Comparison Report is a new report added to compare the traffic represented by an end user transaction before and after an event, such as an upgrade or feature change. |
The following is a list of issues resolved in patches and hotfixes issued for the previous release. These issues are also fixed in this release.
|
Defect ID |
Resolved Issue |
|
APM-6488 |
The "Failed to extract information from record" WARN message is repeated several times a second, filling up the Foglight Management Server log. |
The following is a list of issues known to exist at the time of this release.
The following issues are common to all transaction types.
|
Defect ID |
Known Issue |
|
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-6019 | Issue: Instance Management in a Federated Environment If you use the Manage Monitored Instances dashboard on the Federation Master, be aware that the Master only synchronizes all topology objects once every 30 minutes (by default). Because of this, it is recommended that you work with large time units (days/weeks/months/years) when managing instances on the Master server. If you want to manage instances for shorter intervals, you can make the changes on the Child(ren) Server(s) and wait for the Master to synchronize them. |
| APM-4150 | When you map a component on the Response Time Breakdown Explorer, it may take a few minutes for the mapped component to appear in the component list for related views. |
| APM-4007 | Foglight Federation: If you map a queue to a host on a Child Server, the Master Server synchronizes the mapping. If you later unassign the mapping on the Child Server, the Master Server is not updated. |
| 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-3389, 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, and/or .NET transactions.
The following issues are specific to FxM/FxV transactions.
|
Defect ID |
Known Issue |
| APM-3551 | For drag-and-drop dashboard creation: the FxMApplicationResult and the EUResponseTimeBreakdown are not located in the APM/Transactions node. Workaround: Expand the EndUser root node instead of the APM/Transactions node. |
| APM-3550 | The frontEndTimeMean metric for the EUResponseTimeBreakdown type is not properly localized. |
| APM-3132 | In rare instances, multiple FxV hit filters may source identical transactions in the same time period. If this happens, the execution times of the identical transactions are merged. However, the dependency path only displays the component execution time for one transaction on the path. Therefore, the sum of the component execution times is a fraction of the total execution time displayed. Recommendation: Create one-to-one relationships between FxV hit filters and FxM Application Results. Alternately, ensure that each FxV hit filter sources a distinct transaction per FxM Application Result. |
| 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. The UI for setting up the map agent is designed to prevent this, but setting up a map agent manually can cause this issue. Take special care when setting collection rates to five minute intervals or when importing historical data. This issue is mitigated when an FxM portal is used, as the impacted system will not affect data capture. Check the FxM system health dashboard before deploying a map agent manually. |
| APM-2824 | The application data by location count does not always add up to the total application count. This is because some users could be coming from a location that has a city but no region, or they may have an IP address that does not map to any location (city, country, region). |
| APM-2763 | If a map agent has been created and activated, and has later been deleted after data has been collected, the map agent creation wizard cannot be used to create another map agent. Workaround: Use the map agent ASP configuration method to manually create a new map agent. For more information, see the Monitoring Application Performance User and Reference Guide. |
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. Workaround: Restart the Management Server. | |
| 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. Workaround:
| |
| 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. Workaround: Manually assign the "EU Operator" role to any user that requires access to this dashboard. | |
|
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.7. Upgrades from version 5.9.x, 5.7.x, and 5.6.4.x are supported.
Installing this cartridge also upgrades the following cartridges to the following versions:
Important: Before installing Foglight for Application Operations 5.9.7, you must upgrade the Agent Manager (FglAM) cartridge to version 5.6.10 or later. Only the Agent Manager cartridge needs to be upgraded. You are not required to upgrade any Agent Managers. This is to ensure compatibility with the included Cartridge for Infrastructure.
Foglight for Application Operations must be installed on a running Foglight Management Server 5.6.7 or later.
Foglight Agent Managers of version 5.6.7 or later must be installed on all the hosts that you want to use for local or remote monitoring.
Response Time Breakdown Views: Requires Foglight for Java EE Technologies version 5.8.2 or later, or Foglight for Microsoft .NET version 5.9.1 or later.
Error Breakdown Explorer: Requires Foglight for Java EE Technologies version 5.9.2 or later.
Some functionality included in this cartridge also requires the following:
The following documents provide platform compatibility details:
