RTView® Enterprise Monitor |
|
Known Limitations
Key Metrics
20205: "Response Time" KM for WSM mapped to non-history column
The Response Time key metric for WebSphere (CI Type WAS-APP) is not supported in the Key Metrics History displays at this time.
20324: KM filtering is not supported on tablets
The Filter in the Key Metrics displays cannot be modified when running on a tablet. This is because the Filter is set via popup menu which is not supported on tablets.
Monitor
20157: History Table Statistics does not calculate Deltas until one update cycle passed
The History Table Statistics display will initially show incorrect data for Delta Rows. You must wait one update cycle for this to be resolved.
Platform Support
21636: Agent cannot connect to receiver on OSX
The RTVAgent servlet is not supported on Mac OS X.
Scripts
20838: "stop_rtv all" does not include a server listed after "viewer/builder" lines
Documentation clarification: The rtvservers.dat file contains groups of servers called a "config", associated by a common name, e.g. "central". Such groups must be contiguous in the file. That is to say, a config may not be split up in the file; all the servers it includes must appear contiguously.
Solution Package
Docker
21559: Unable to remove a stopped container in Docker: 'device or resource busy'
If cAdvisor is started after other containers, it prevents Docker from removing those containers. If cAdvisor is the first container loaded into Docker, then other containers can be removed without any issue. The workaround is to start the cAdvisor before any other container.
TIBCO Hawk
20568: HawkAlerts cache sometimes out of sync with with alerts in the Hawk Display
There are 2 cases where the HawkAlerts cache may not be in sync with the Hawk Alerts on an agent: 1. If RTView does not receive any updates for a HawkAlert for the amount of time specified in $rtvHawkAlertClearTime + $rtvHawkAlertDeleteTime (defaults to 10 days + 1 hour), it is removed from the HawkAlerts cache. 2. When using a sender to update the HawkAlerts cache, any events that occur when the sender is running but the receiver is not will be missed. To fix this, restart the sender after any restart of the receiver.
VMWare vSphere
20594: MySQL historian requires NO_BACKSLASH_ESCAPES
The VMWMON package collect metrics about disk usage on Windows systems, which results in the backslash (\) character being present in the data collected. MySQL databases will not correctly store data with a backslash (\) unless the NO_BACKSLASH_ESCAPES mode is enabled.
|
|