ARMS alert management has been upgraded with an improved UI and new capabilities. Learn what changed between the new and legacy versions.
New features
Notification policies dispatch, process, and route alert events. When a rule triggers, the system notifies your specified contacts.
Add an escalation policy to re-notify contacts when alerts remain unresolved for a specified period.
Alerts are sent as interactive cards to DingTalk groups. You can silence or claim alerts directly in the group.
The new module integrates with ARMS by default. You can also centralize alerts from Prometheus, Log Service, and CloudMonitor into ARMS.
Changes
- Alert Policies page
The legacy Alert Policies page and its alert rule creation entry point have been removed. Manage alert rules on the respective pages for each sub-service.
- Alert Rules page
The legacy Alert Rules page has been removed. New pages in Browser Monitoring and Application Monitoring let you create, view, edit, and manage alert rules by type.
- Notification methods
Legacy notification settings—contacts, templates, recovery notifications, silence periods, and validity periods—are replaced by notification policies. To modify them, use Quick Migration on the rule edit page to convert them into a notification policy.
- The alert template management feature has been retired.
- Default alert rule creation
Default alert rules are no longer automatically created for newly imported Application Monitoring applications and Browser Monitoring sites.
Alert Policies page
Alert Rules page
Notification methods
Before the upgrade, you configured notifications within each alert rule—selecting contacts and groups, setting a template, silence period, and validity period.
After the upgrade, notification policies handle alert notifications. A policy specifies dispatch rules, event grouping, contacts, notification methods, templates, and silence/escalation settings. When creating an alert rule, select or create a notification policy instead of configuring notification details directly.
Create notification policies in advance, then select one when creating alert rules. Alternatively, create rules without a policy first, then add a broad policy later to match alerts from multiple rules.
- For unmigrated legacy alert rules, alert events and sending history are not visible in the new UI. To view them, navigate to the page and click Back to Previous Version.
- When editing a legacy alert rule, notification settings are no longer editable. Click Quick Migration on the edit page to convert them into a notification policy. Note:
- Review the auto-created notification policy. New features use default values that you can adjust as needed.
- After switching to a notification policy, alert notification format changes. If you use DingTalk group notifications, verify that configured keywords appear in the new content, or the group will not receive alerts.
- Alert rules and notification policies are loosely coupled. Multiple policies can match events from one rule, and one policy can match events from multiple rules.
Alert template removal
The alert template feature has been retired. Instead, apply a single alert rule to multiple applications simultaneously.
Default alert rule creation
Before the upgrade, when you created or imported Application Monitoring applications, Browser Monitoring sites, and Prometheus clusters, ARMS automatically created default alert rules based on templates.
After the upgrade, default alert rules are no longer created automatically for new Application Monitoring applications and Browser Monitoring sites. Existing default rules continue to run. When you create or import a Prometheus cluster, ARMS still automatically creates a default Prometheus alert rule.