The Alert Management module in Enterprise Distributed Application Service (EDAS) has been upgraded with notification policies, escalation policies, and DingTalk group notifications. Some features have been removed or relocated.
This guide covers what changed and how to migrate your existing alert configurations.
Changes overview
The following table summarizes the differences between the old and new Alert Management modules.
| Area | Old module | New module |
|---|---|---|
| Alert rules | Managed on a dedicated Alert Rule page | Managed under Alert Management > Alert Rule in the Application Monitoring module |
| Notification settings | Configured per alert rule: contacts, templates, alert clearance notifications, intervals, and validity period | Configured through notification policies |
| Alert templates | Available for creating rules across multiple applications | Removed. Apply a single alert rule to multiple applications instead |
| Default alert rules | Automatically created for new applications in Application Monitoring | No longer created automatically. Existing default rules still work |
New features
Notification policies
Notification policies centralize how alert events are dispatched, handled, and delivered. When an alert rule triggers, EDAS sends notifications to the contacts you specify, using the notification method you configure.
For more information, see Notification policies.
Escalation policies
If an alert remains unresolved, an escalation policy automatically notifies contacts. Configure escalation policies within your notification policies to make sure critical alerts get attention.
For more information, see Configure an escalation policy.
DingTalk group notifications
Send alert notifications to DingTalk groups as interactive cards. Group members can block or claim alerts directly from the DingTalk conversation.
For more information, see Alert notifications in DingTalk groups.
Manage alert rules
After the upgrade, go to Alert Management > Alert Rule to create, view, edit, and manage alert rules for application monitoring.
Migrate notification settings
The upgrade introduces notification policies as the single place to manage all notification-related settings. The old per-rule notification settings (contacts, templates, alert clearance notifications, intervals, and validity period) are read-only in the new module.
To update these settings, migrate them to the Notification policy page.
Migration workflow
Create notification policies. Define dispatch rules, contacts, notification methods, templates, repeat intervals, and escalation policies in a notification policy.
Create or update alert rules. Select an existing notification policy when you create a new alert rule.
Alternatively, create alert rules without specifying a notification policy. Then configure dispatch rules with fuzzy match in a notification policy to automatically match alert events from those rules.
Post-migration checklist
When you migrate old notification settings, EDAS automatically creates notification policies from those settings. Review the auto-generated policies:
Check default values. EDAS sets some newly added parameters to defaults. Adjust these to match your requirements.
Verify DingTalk chatbot keywords. The migration may change the format and content of alert notifications. If you use a DingTalk chatbot, make sure the notification content still contains the keyword you configured. Otherwise, the DingTalk group does not receive alerts.
Understand the many-to-many relationship. Alert rules and notification policies are not one-to-one. A single notification policy can apply to events from multiple alert rules. Conversely, events from one rule can be routed to different notification policies through dispatch rules.
For alert rules created in the old module that are not yet associated with a notification policy, you cannot view their alert events or notifications in the new module. To access this historical data, go to Alert Management > Alert sending History and click Previous Version.
Removed features
Alert templates
The alert template feature has been removed. To get similar coverage, apply a single alert rule to multiple applications.
Default alert rules
In the old module, EDAS automatically created default alert rules based on the alert templates when you added an application or application cluster to Application Monitoring. After the upgrade, default alert rules are no longer created automatically. Existing default alert rules continue to work.