Supported events
The Application Real-Time Monitoring Service (ARMS) agent for Java v4.x and later automatically collects the following events and sends them to the Alert Management sub-service.
|
Event |
Alert level |
Description |
|
Critical Error Detected |
Critical (P1) |
A critical java.lang.Error, such as java.lang.OutOfMemoryError, occurred during instrumentation. |
|
Dead lock detected |
Critical (P1) |
A deadlock occurred. |
|
Java Agent Bootstrap Success |
Page (P4) |
The agent started as expected. |
|
Heap dump success |
Page (P4) |
The memory dump succeeded. |
|
Heap dump failure |
Page (P4) |
The memory dump failed. |
|
Profiling start success |
Page (P4) |
Continuous profiling started successfully. |
|
Profiling start failure |
Page (P4) |
Continuous profiling failed to start. |
To view event details, see Alert event analysis.
Cancel alerting for events reported by the agent
If you configured a global fallback notification policy, all events reported by the Java v4.x agent trigger notifications. To exclude specific events, adjust the policy by adding matching conditions. For example, to stop notifications for Java Agent Bootstrap Success and Profiling Start Success, add the conditions alertname Not In Java Agent Bootstrap Success and alertname Not In Profiling start success.