Application Real-Time Monitoring Service:Notification policies

Create a notification policy

1. Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Notification Policies.

2. On the Notification Policies page, click Create Notification Policy.

3. At the top of the Create Notification Policy page, enter a policy name.

4. In the Matching Rule section, set a matching rule for alert events.

   Important

   Silence policies take precedence over notification policies. If an alert event matches a silence policy, the event is silenced and is not matched by any notification policy. For more information about how to create a silence policy, see Silence policies.

   1. Select a data source.

      • Specific source: The policy filters alert events from a specified integration and sends notifications based on the matching rules.

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

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

      Existing tags include the following:

      • Tags from the metrics of the alert rule expression. For information about how to create tags for an alert rule in Managed Service for Prometheus, see Create a Prometheus alert rule.

      • Default tags provided by ARMS. The following table describes the default tags.

        Category	Tag	Description
        Common fields	alertname	The name of the alert.
        	clustername	The name of the cluster.
        	severity	The severity level of the alert: P1 P2 P3 P4 Default
        	namespace	Namespace.
        	pod_name	Pod name.
        System preset fields	_aliyun_arms_integration_name	The name of the integration. The default integration name 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 ID of the alert rule.
        	_aliyun_arms_alert_type	The type of the alert rule: 101: Prometheus alert 5: Application Monitoring alert 4: Browser Monitoring alert

      Note

      • To trigger an alert only when multiple conditions are met, click Add Condition to add another condition to the same rule.

      • To trigger an alert when any of the rules are met, click Add Rule to add another matching rule.

      • When you configure matching rules for a notification policy, the total size of all rule descriptions cannot exceed 64 KB. This limit is equivalent to approximately 100 rules, but the exact number depends on their complexity. If the limit is exceeded, the configuration fails. In this case, you must create a new notification policy for the additional rules.

   3. Click Next.

5. In the Event Grouping section, specify whether to group alert events, and then click Next.

   • Do not group: Each alert event is sent as a separate alert notification to the handler.

   • Set grouping fields: Alert events with the same content in the specified fields are aggregated into a single alert notification.

6. In the Notification Objects section, set the following parameters.

   1. Click +Add Notification Recipient to select notification recipients.

      The following types of notification recipients are available:

      • Contact: After you select a contact, select a notification method: phone call, text message, or email.

      • Contact Group: After you select a contact group, select a notification method: phone call, text message, or email.

      • On-call Schedule: After you select a schedule, select a notification method: phone call, text message, or email.

      • DingTalk/Lark/WeCom: Send alert notifications using DingTalk, Lark, or WeCom.

      • General Webhook: Send alert notifications using a webhook.

   2. Specify whether to send a recovery notification after an alert is recovered.

      Send recovery notification: If you enable this option, the system sends a notification to the alert handler when the alert is recovered. An alert is considered recovered after all related events are resolved and its status automatically changes to Resolved.

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

   4. Set the notification period. Alert notifications are sent only within the specified period.

   5. Optional: Select a ticket system to which you want to push alerts. For more information about integrating a ticket system, see Integrations.

   6. Click Next.

7. In the Repeat/Escalate/Recover Policy section, specify whether to resend notifications or use an escalation policy, and then click Next.

   • Resend notifications: If you enable this option, you must set the resend frequency. If an alert is not recovered, the alert information is sent repeatedly at the specified frequency until the alert is recovered.

   • Configure an escalation policy for alerts:

     No escalation policy: The notification is sent only once, even if the alert is not recovered.

     Use escalation policy: If the alert is not recovered, notifications are sent to other notification objects based on the escalation policy.

   • Enable manual recovery: If you enable this option, an alert is not automatically recovered even if no alert event is triggered within the automatic recovery time that is set in the alert integration. You must manually change the status of the alert.

8. In the Action Integration section, you can set actions to be automatically executed when an alert is triggered or recovered. For more information, see Execute an alert plan using an ARMS action integration.

9. After you complete the configuration, click Save.

Manage notification policies

After you create a notification policy, it appears 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. After you modify the policy, click Save.

• Enable or disable a notification policy: In the Status column for the policy, toggle the switch.

• Delete a notification policy: Click Delete in the Actions column. In the dialog box that appears, click Confirm.

• Copy a notification policy: Click Copy in the Actions column to create a duplicate policy.