Supported events
The Application Real-Time Monitoring Service (ARMS) agent for Java v4.x and later automatically collects the following events and pushes them to the Alert Management sub-service.
Event | Alert level | Descriptin |
Critical Error Detected | Critical (P1) | A critical java.lang.Error 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 was executed as expected. |
Heap dump failure | Page (P4) | The memory dump failed to be executed. |
Profiling start success | Page (P4) | Continuous profiling started as expected. |
Profiling start failure | Page (P4) | Continuous profiling failed to be started. |
You can view the event details in the Alert Management sub-service. For more information, see Alert event analysis.
Cancel alerting for events reported by the agent
If you have configured a global fallback notification policy, all events reported by the agent for Java v4.x will trigger notifications. To prevent unnecessary notifications, you can adjust the policy to exclude specific events. For instance, to stop notifications for the Java Agent Bootstrap Success and Profiling Start Success events, you can add the following matching conditions: alertname Not In Java Agent Bootstrap Success and alertname Not In Profiling start success.
