App Visibility health event severity
Many App Visibility Manager health events have the severity of Minor or Warning, representing temporary or isolated occurrences. For example, an invalid agent policy, or an agent that stop or starts, are events with the severity of Warning.
The following events have a severity of Major:
- App Visibility collector database is down
- App Visibility collector failover
- App Visibility collector experiencing high memory consumption
- App Visibility collector is down
- App Visibility collector standby node is down
- App Visibility portal database is down
- App Visibility portal failover
- App Visibility portal standby node is down
- App Visibility proxy is down
- Synthetic TEA Agent is down
When an issue is corrected, a closing event is automatically sent.
All App Visibility health events and TEA Agent events, no matter what the severity, are sent to the health-events.csv file, located on the portal computer in the portalInstallationDirectory\portal\logs\events directory.
To adjust the severity at which to send App Visibility health events
By default, App Visibility sends health events that have a severity of Major or Critical to integrated systems, such as TrueSight Information Management. You can adjust the severity at which to send health events. The setting only affects sending health events to integrated systems. All App Visibility health events and TEA Agent events, no matter what the severity, are sent to the health-events.csv file.
- On the App Visibility portal computer, open the portal.properties file, located in the following directory:
- Change the value of the
Valid values are
- Save the file and restart the portal service.
Where to go from here
Confirm that App Visibility health events are displayed at the severity you set in the integrated system. For example, with an Infrastructure Management integration, confirm that the health events are displayed on the in the TrueSight console.