The Application Real-Time Monitoring Service (ARMS) Alert Management module has been upgraded to separate notification logic from alert rules. Notifications are now managed through reusable notification policies, with added support for escalation, DingTalk group alerts, and external monitoring integrations.
Existing alert rules continue to trigger and send notifications after the upgrade. However, notification settings on pre-upgrade alert rules become read-only. To modify them, migrate to a notification policy.
What changed
Concept mapping: before and after the upgrade
The upgrade restructures how alert rules relate to notifications. Previously, notification settings were configured directly on each alert rule. Now, notification policies are separate, reusable objects that decouple alert rules from notification logic.
| Before the upgrade | After the upgrade |
|---|---|
| Notification settings embedded in each alert rule (contacts, templates, silence period, validity period) | Notification policies manage all notification settings separately |
| Alert templates used to create rules across applications | Apply a single alert rule to multiple applications (alert templates removed) |
| Default alert rules auto-created for Application Monitoring, Browser Monitoring, and Prometheus Monitoring | Default alert rules auto-created only for Prometheus Monitoring |
Navigation changes
| Before the upgrade | After the upgrade |
|---|---|
| (for Application Monitoring, Browser Monitoring, Custom Monitoring, and Prometheus Monitoring) | Removed. Manage alert rules under each sub-service |
| Removed | |
| N/A | |
| N/A |
Alert rules created in both the old and new Application Monitoring and Browser Monitoring sub-services are merged into the new pages.
Prometheus Monitoring alert rules
The old Prometheus Monitoring alert rule feature is still available but no longer maintained. To access it:
In the left-side navigation pane, choose .
Click the target cluster.
In the cluster navigation pane, click Alert Rules.
On the Prometheus Alert Rules page, click Back to Previous Version, and then click Create Alert Rule.
New capabilities
The upgraded Alert Management module introduces four capabilities:
| Feature | Description |
|---|---|
| Notification policy | Routes alert events to the right contacts through configurable dispatch rules, grouping, notification methods, and silence periods. Replaces per-rule notification settings from the previous version. |
| Escalation policy | Automatically escalates unresolved alerts to additional contacts after a specified period |
| DingTalk group notifications | Sends alert notifications to DingTalk groups as interactive alert cards that support blocking and claiming alerts |
| Integration | Integrated with ARMS by default. Connects external monitoring services -- such as open source Prometheus, Simple Log Service (SLS), and CloudMonitor -- to ARMS Alert Management |
Migrate notification settings
After the upgrade, notification settings on alert rules created in the old Alert Management sub-service are read-only. These settings include:
Alert contacts and contact groups
Notification templates
Alert clearance notifications
Intervals between repeated notifications
Validity period
Migration steps
Open the alert rule for editing.
Click Quick Migration to move the notification settings to the Notification Policy page.
Review the migrated notification policy. The system sets some new parameters to default values -- verify that these defaults meet your requirements.
Save the notification policy.
After migration, the format and content of alert notifications may change. If you use DingTalk group chats with keyword filtering, make sure the notification content on the Notification Policy page includes the required keywords. Otherwise, DingTalk groups will not receive notifications.
View alert history for unmigrated rules
Alert events and notification records for old alert rules that are not associated with a notification policy cannot be viewed in the new Alert Management sub-service.
To view these records: choose in the left-side navigation pane, and then click Previous Version.
How alert rules and notification policies work together
Alert rules and notification policies are loosely coupled. A single alert event can be handled by multiple notification policies, and a single notification policy can handle events from different alert rules. This decoupled design supports the following patterns:
Reuse one notification policy across many alert rules
Apply different notification strategies to the same alert rule through dispatch conditions
Route alert events automatically with fuzzy match in dispatch rules, without explicit rule-to-policy associations
Set up new alert rules
Create notification policies before creating alert rules. When you create a new alert rule, select an existing notification policy to handle its events.
Alternatively, create alert rules first without assigning a notification policy, and then configure dispatch rules with fuzzy match to automatically route matching alert events to the appropriate notification policy.
Removed features
| Feature | Replacement |
|---|---|
| Alert Policies page and Create Alert tab | Manage alert rules under Application Monitoring Alert Rules and Browser Monitoring Alert Rules |
| Alert Rules page (centralized) | Alert rules pages under each sub-service |
| Alert template management | Apply an alert rule to different applications directly |
| Default alert rules for Application Monitoring and Browser Monitoring | Create alert rules manually. Existing default rules continue to trigger. Prometheus Monitoring still auto-creates default alert rules. |