All Products
Search
Document Center

Managed Service for OpenTelemetry:Notification policies

Last Updated:Aug 24, 2026

A notification policy defines the matching rules for alert events. When an alert event matches a rule, the system sends an alert notification to the notification objects that you specify, through the notification methods that you configure, so that the recipients can act on the issue.

Prerequisites

Required

Prepare as needed

Prepare the following resources before you complete the wizard, based on the options that you plan to configure:

  • A notification template, which you configure in the Notification Objects step.

  • A ticketing system integration, if you push alerts to a ticketing system in the Notification Objects step.

  • An escalation policy, if you escalate uncleared alerts in the Policy to Repeat/Escalate/Clear Alerts step.

  • An alert integration that specifies the auto-recovery period, if you enable manual recovery in the Policy to Repeat/Escalate/Clear Alerts step.

Considerations

Review the following behavior before you create a notification policy for alert events.

Important

Silence policies take precedence over notification policies. An alert event that matches a silence policy is suppressed and is no longer evaluated against notification policies. To learn how to create a silence policy, see silence policy.

Create a notification policy

  1. Log on to the Managed Service for OpenTelemetry console. In the left-side navigation pane, choose Alert Management > Alarm policy.

  2. Click the Notification Policies tab, and then click Create Notification Policy. On the page that appears, enter a name for the policy.

  3. In the Matching Rule section, configure the matching rules for alert events.

    1. Select a data source.

      • Specified source: The notification policy filters alert events from the specified source (integration) against the matching rules and sends notifications.

      • No preset source: The notification policy filters all alert events against the matching rules and sends notifications.

    2. Set the matching rule expression. You can define custom tags or select existing tags.

      Existing tags include:

      • Tags carried by the metrics in an alert rule expression. For information about how to create tags for alert rules in Managed Service for Prometheus, see Prometheus alert rules.

      • Default tags provided by Application Real-Time Monitoring Service (ARMS). For the tag names and their descriptions, see the Default tags section of this topic.

      Note

      You can combine multiple matching conditions in one policy:

      • To trigger an alert only when multiple matching rules are met at the same time, click Add Condition and configure a second matching rule condition.

      • To trigger an alert when any matching rule is met, click Add Rule and configure a second matching rule.

    3. Click Next.

  4. In the Event Group section, specify whether alert events are grouped, and then click Next.

    • Do not group: All alert events are sent to the recipient in a single alert notification.

    • Set group-by fields: Alert events that have the same field values are aggregated into a single alert notification.

  5. In the Notification Objects section, configure the following parameters.

    1. Click + Add notification object to select notification objects.

      Notification object types:

      • Contact, Contact group, or Shift: After you select the object, select a notification method: phone call, SMS, or email.

      • DingTalk/Lark/WeCom or Webhook: Alert notifications are sent through the DingTalk, Lark, WeCom, or webhook channel that you select.

    2. Specify whether to send a clearing notification after an alert is cleared.

      Send clearing notification: Controls both the alert status and the clearing notification. When this option is enabled, the alert status is automatically changed to Resolved after all events of the alert are cleared, and the system sends a notification to the alert handler.

    3. Configure a notification template. For more information, see Configure notification templates and webhook templates.

    4. Set a notification time range. Alert notifications are sent only during the specified time range.

    5. (Optional) Select the ticketing system to which alerts are pushed. For information about how to integrate a ticketing system, see action integration.

    6. Click Next.

  6. In the Policy to Repeat/Escalate/Clear Alerts section, specify whether to repeat alert notifications or apply an escalation policy, and then click Next.

    • Repeat alert notifications: Set the repeat interval. If the alert is not cleared, the system resends the alert notification at the specified interval until the alert is cleared.

    • Escalation policy: After you select an escalation policy, notifications are sent to other notification objects based on the policy while the alert remains uncleared.

    • Manual recovery: If you enable manual recovery, the alert is not automatically cleared even when no alert event is triggered again within the auto-recovery period that is specified in the alert integration. You must manually update the alert status.

    • In the Action Integration section, you can configure the actions that run automatically when an alert is triggered or cleared. For more information, see Execute an alert playbook by using action integrations.

  7. After you complete the configuration, click Save.

    The new policy appears on the Notification Policies page. If alert notifications do not arrive for an alert event that the policy matches, check whether a silence policy suppresses the event, as described in the Considerations section, and whether the event occurs within the notification time range that you set.

Manage notification policies

After a notification policy is created, it is displayed on the Notification Policies page. On the Notification Policies page, you can perform the following operations:

  • Edit a notification policy: Click the policy name, or click Edit in the Actions column on the right. After you modify the policy, click Save.

  • Enable or disable a notification policy: Turn on or turn off the switch in the Status column on the right of the policy.

  • Delete a notification policy: Click Delete in the Actions column on the right of the policy, and then click Confirm in the dialog box that appears.

  • Copy a notification policy to create an identical one: Click Copy in the Actions column on the right of the policy.

Default tags

The following table describes the default tags that ARMS provides. You can select these tags when you set a matching rule expression for a notification policy.

Category

Tag

Description

Common fields

alertname

The alert name.

clustername

The cluster name.

severity

The alert severity. Valid values: P1, P2, P3, P4, and Default.

namespace

The namespace.

pod_name

The pod name.

System-preset fields

_aliyun_arms_integration_name

The integration name. The default integration name for alerts reported by ARMS is ARMS-DEFAULT.

_aliyun_arms_involvedObject_id

The ID of the alert object.

_aliyun_arms_involvedObject_name

The name of the alert object.

_aliyun_arms_region_id

The region ID.

_aliyun_arms_alert_rule_id

The alert rule ID.

_aliyun_arms_alert_type

The alert rule type. Valid values: 101 (Prometheus alert), 5 (Application Monitoring alert), and 4 (Browser Monitoring alert).