When alert rules trigger events across your monitored applications and infrastructure, you need a centralized place to investigate past incidents and identify recurring patterns. The Alert Event History page in Application Real-Time Monitoring Service (ARMS) records every alert event triggered by your alert rules, regardless of resolution status. Use this page to track alert patterns, investigate root causes, and verify that your monitoring coverage works as expected.
Concepts
ARMS organizes alerting into the following hierarchy:
| Concept | Description |
|---|---|
| Alert rule | Defines the conditions under which an alert event is triggered. |
| Alert event | A record generated when an alert rule's conditions are met. Events accumulate on the Alert Event History page. |
| Notification policy | Controls how and when you are notified about alert events. |
Open the Alert Event History page
Log on to the ARMS console.
In the left-side navigation pane, choose Alert Management > Alert Event History.
The Events page lists all historical alert events.

Each row contains the following columns:
| Column | Description |
|---|---|
| Name | Alert event name, derived from the alert rule that triggered it. |
| Notification policy | Notification policy associated with the alert event. |
| Generated at | Timestamp when the alert event was first triggered. |
| Count | Number of events with the same name. |
| Status | Current state of the alert event. See the table below for definitions. |
| Object | Monitored resource that triggered the alert, such as a monitoring task or cluster. |
| Object type | Type of the monitored resource. |
Event status reference
| Status | Meaning |
|---|---|
| Not recovered | The alert condition persists. An alert is generated each time the event is detected. |
| Silent | The alert condition persists but notifications are suppressed. Within the specified time range, an alert is generated only when the event is first detected. |
| Restored | The alert condition has cleared. Within the specified time range, no alerts are generated when the event is detected. |
Search for alert events
Filter the event list to locate specific alert events.
On the Events page, set one or more filter conditions:
Filter Description Event Name Name of the alert rule that triggered the alert. Integration Name Name of the service integration that reported the alert event. Event Status Alert event status: Not recovered, Silent, or Restored. Event Object Name of the monitored resource involved in the alert event. Object Type Type of the monitored resource involved in the alert event. Integration Type Type of the service integration that reported the alert event. Click Search.
The event list updates to show only matching results.
View alert event details
Click an alert event name on the Events page to open the Event Details page.

The page contains three sections:
| Section | Description |
|---|---|
| Basic information | Metadata about the alert event, including the alert rule, current status, and the triggering object. |
| Monitoring data | A time-series chart showing metric behavior around the time the alert fired. Use this chart to identify the conditions that led to the alert. |
| Extended fields | Additional attributes associated with the alert event. |
Adjust the monitoring data time range
By default, the monitoring data chart displays a narrow window around the alert trigger time. To expand the view:
Select 6 Hours, 12 Hours, or 1 day from the time range drop-down list to view a wider period before and after the alert.
Drag across the chart to zoom into a specific interval. Click Reset to return to the original view.
Send a test event
Send a test alert event to a service integration to verify that the integration is configured correctly.
On the Events page, click Send Test Events.
In the dialog box, configure the following fields:
Integration Name: Select the target service integration.
Event Content: Enter the test event payload.
Click OK.
ARMS sends the test event to the selected integration. Check the integration's receiving endpoint to confirm delivery.