Configure a notification policy

How it works

1. An alert rule triggers an alert event.

2. EDAS evaluates the event against each notification policy's matching rules.

3. If a match is found, EDAS groups the event based on the policy's event handling settings.

4. EDAS sends notifications to the configured contacts through the selected channels.

Create a notification policy

1. Log on to the EDAS consoleEDAS console.

2. In the left-side navigation pane, click Application Management > Applications. In the top navigation bar, select a region. In the upper part of the page, select a namespace. Select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, find the application that you want to deploy and click the application name.

3. In the top navigation bar, select a region. In the upper part of the page, select a namespace.

4. From the Cluster Type drop-down list, select Container Service or Serverless Kubernetes Cluster. Find your application and click its name.

5. In the left-side navigation pane, choose Alert Management > Notification Policy.

6. Click Create Notification Policy in the upper-right corner.

7. Enter a name for the notification policy in the top field.

8. Define matching rules

   In the Match Alert Event Rules section, define which alert events trigger this policy.

   1. Set the event source filter.

      • To restrict the policy to a specific alert source, select the source from the drop-down list. Only events from that source are processed.

      • To apply the policy to all alert events regardless of source, select Do not filter sources.

   2. Add dispatch conditions.

      Specify field-based conditions to further filter alert events. Select an existing field or define a custom field, then set the matching criteria.

      Example: alertname is equal to PodRestart.

      The following default fields are available:

      Field	Description
      alertname	Alert name. Format: <alert-name>_<cluster-name>
      _aliyun_arms_alert_level	Alert level
      _aliyun_arms_alert_type	Alert type
      _aliyun_arms_alert_rule_id	Alert rule ID
      _aliyun_arms_region_id	Region ID
      _aliyun_arms_userid	User ID
      _aliyun_arms_involvedObject_type	Subtype of the associated object, such as ManagedKubernetes or ServerlessKubernetes
      _aliyun_arms_involvedObject_kind	Type of the associated object, such as app or cluster
      _aliyun_arms_involvedObject_id	ID of the associated object
      _aliyun_arms_involvedObject_name	Name of the associated object

      In addition to default fields, these field types are supported:

      • Fields included in an alert rule expression

      • Fields created in Managed Service for Prometheus alert rules

   3. Combine multiple conditions.

      • To require all conditions to be met (AND logic), click + condition to add conditions within the same rule.

      • To match any one of several conditions (OR logic), click + add rule to create a separate dispatch rule.

      

9. Configure event handling

   In the Event Handling section, define how matched alert events are processed.

   

   Parameter	Description
   Processing Method	Generate Alerts: Alert notifications are created and sent to contacts. Do Not Generate Alerts (Drop Events): Alert events are silently dropped and no notifications are sent.
   Event Group	Do not group: All alerts are sent in a single notification. Specifies that events with the same field content are assigned to a group: Select fields to group alert events. Events with matching field values are bundled into one notification.
   Automatic Alert Recovery	When enabled, the alert status automatically changes to resolved after all related events are resolved. Contacts are notified of the status change.

10. Set up notifications

    In the When an alert is triggered section, configure how and when contacts are notified.

    

    Parameter	Description
    Contacts	Select one or more contacts, contact groups, or DingTalk groups to receive notifications. For more information, see Create a contact.
    Notification Method	Choose one or more delivery channels: DingTalk, Email, Text messages, phone calls, or WebHook. To customize the notification content, click Notification template to configure templates for email, text message, or phone notifications. Note Phone call notifications require a verified phone number. For more information, see Verify a mobile number.
    Notification Period	The time range during which alert notifications are repeatedly sent.
    Update Notification Method	Choose how to handle alerts that remain unresolved. Recurring Notifications: Specify the interval at which notifications are resent until the alert is resolved. Escalation Policy: Select an existing escalation policy or create one. For more information, see Create and manage an escalation policy. To view policy details, click Details.
    Ticket System	The ticket system to which alert notifications are forwarded.

11. Save the policy

    Click the save icon () in the upper-right corner to save the notification policy.

Manage notification policies

After creation, notification policies appear in the Notification Policies section. To manage a policy:

• From the list: Click the More icon next to a policy and select Edit, Disable, Enable, Copy, or Delete.

• From the detail view: Click a policy name to open it, then use the icons in the upper-right corner to modify, refresh, copy, or delete the policy.

What's next

• Create a contact

• Create and manage an escalation policy