The Application Real-Time Monitoring Service (ARMS) agent for Java v4.x and later automatically collects runtime events and reports them to Alert Management. These events cover critical errors, deadlocks, agent lifecycle status, and profiling operations.
Supported events
| 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 in the application. |
| Java Agent Bootstrap Success | Page (P4) | The agent started successfully. |
| Heap dump success | Page (P4) | A heap dump completed successfully. |
| Heap dump failure | Page (P4) | A heap dump failed. |
| Profiling start success | Page (P4) | Continuous profiling started successfully. |
| Profiling start failure | Page (P4) | Continuous profiling failed to start. |
View event details on the Alert event analysis page in Alert Management. For more information, see Alert event analysis.
Exclude agent events from alert notifications
If you configure a global fallback notification policy, every event the Java agent reports triggers a notification. To suppress notifications for specific events, add matching conditions that exclude them from the notification policy. Use the event name from the Event column in the preceding table as the alertname value.
For example, to stop receiving notifications for the Java Agent Bootstrap Success and Profiling start success events:
Go to your global fallback notification policy.
Add the following matching conditions:
alertname Not In Java Agent Bootstrap Successalertname Not In Profiling start success
