The Alert Management module in Enterprise Distributed Application Service (EDAS) has been upgraded. Notification settings are now managed through reusable notification policies instead of per-rule configuration. The upgrade also adds escalation policies and DingTalk group alerting, and removes alert templates and auto-created default alert rules.
Alert rules created before the upgrade continue to trigger and send notifications as expected. No action is required for existing rules to keep working.
What changed
| Area | Before upgrade | After upgrade |
|---|---|---|
| Notification settings | Configured directly on each alert rule (contacts, templates, repeat intervals, validity periods). | Read-only on old rules. Create notification policies to manage these settings centrally. |
| Alert Rules page | Previous UI. | Updated UI for creating, viewing, and managing alert rules for application monitoring. |
| Alert templates | Available. Apply a template to create rules for multiple applications. | Removed. Apply a single alert rule to multiple applications instead. |
| Default alert rules | EDAS auto-creates default alert rules when you create or import applications with monitoring enabled. | EDAS no longer auto-creates default rules. Existing default rules still trigger. |
| Notification policies | Not available. | New. Define how alert events are dispatched, grouped, and sent to contacts. |
| Escalation policies | Not available. | New. Escalate unresolved alerts to additional contacts after a specified period. |
| DingTalk group alerts | Not available. | New. Send alert notifications as cards to DingTalk groups. Block or claim alerts directly in the group. |
How notification policies work
Previously, each alert rule contained its own notification settings -- contacts, templates, repeat intervals, and validity periods. The upgrade separates notifications from alert rules through notification policies, which serve as reusable, centralized notification configurations.
A notification policy defines:
Dispatch rules -- which alert events to match (supports fuzzy match)
Grouping -- how to combine related alert events
Contacts and notification methods -- who to notify and how
Notification templates -- the content format for alert messages
Repeat intervals -- how often to resend notifications for unresolved alerts
Escalation policies -- who to escalate to if alerts remain unresolved
Relationship between alert rules and notification policies
Alert rules and notification policies have a many-to-many relationship:
One notification policy can serve multiple alert rules.
Events from a single alert rule can route to different notification policies through dispatch rules.
This separation means you configure notification behavior once in a policy and reuse it across any number of alert rules, rather than duplicating settings on each rule.
Migrate notification settings to notification policies
After the upgrade, notification settings on old alert rules are read-only. To modify them, migrate the settings to notification policies.
Choose a migration approach
| Approach | When to use | How it works |
|---|---|---|
| (Recommended) Create notification policies first | You want full control over dispatch, grouping, and escalation before alerts fire. | Create notification policies, then select them when configuring alert rules. |
| Create alert rules first | You prefer automatic matching. | Create alert rules without specifying policies, then create notification policies with fuzzy-match dispatch rules that automatically match alert events. |
Migration steps
In the left-side navigation pane, choose Alert Management > Alert Rules.
Identify alert rules created in the old module that need updated notification settings.
Navigate to the Notification policy page. EDAS automatically creates notification policies from old notification settings when you initiate migration.
Review the auto-generated notification policies. Verify all settings, especially newly added parameters that EDAS sets to default values.
Adjust the notification policies to match your requirements, then save.
Old-to-new settings mapping
The following table shows how old per-rule notification settings map to fields in notification policies:
| Old notification setting | New notification policy field |
|---|---|
| Alert contacts / contact groups | Contacts and notification methods |
| Notification template | Notification templates |
| Repeat notification interval | Repeat intervals |
| Validity period | Dispatch rules (time-based matching) |
| Alert clearance notification | Notification templates (clearance format) |
| (Not available) | Dispatch rules (event matching) |
| (Not available) | Grouping |
| (Not available) | Escalation policies |
After migration, the format and content of alert notifications may change. If you use a DingTalk chatbot, verify that the notification content still contains the keyword configured for the chatbot. Otherwise, the DingTalk group will not receive notifications.
View legacy alert history
Alert events and notifications for old alert rules not yet associated with notification policies are only accessible through the legacy view:
In the left-side navigation pane, choose Alert Management > Alert sending History.
Click Previous Version to view historical alert data.
New features
Notification policies
Notification policies centralize alert notification dispatch and delivery. Instead of configuring notification settings on each alert rule, create reusable notification policies that apply across multiple rules.
To create a notification policy, see Create a notification policy.
Escalation policies
Escalation policies route unresolved alerts to additional contacts. When an alert remains open beyond a specified time, EDAS sends notifications to the escalation contact through the method defined in the policy.
To set up escalation, see Create and manage an escalation policy.
DingTalk group alerts
Send alert notifications as interactive cards to DingTalk groups. Recipients can block or claim alerts directly from the card without leaving the conversation.
For setup instructions, see Alert notifications in DingTalk groups.
Removed features
Alert templates
The alert template feature is no longer available. As an alternative, apply a single alert rule to multiple applications.
Default alert rules for new applications
In the old module, EDAS automatically created default alert rules based on alert templates when you created or imported applications with application monitoring enabled. After the upgrade, EDAS no longer creates these default alert rules. Existing default alert rules continue to trigger normally.
What's next
Create a notification policy to centralize alert notification settings
Create and manage an escalation policy for unresolved alerts
Set up DingTalk group alerts for team-based alert handling