Managed Service for Prometheus:Create and manage a notification policy

Create a notification policy

This procedure walks through five configuration stages: matching rules, event grouping, notification objects, repeat/escalation behavior, and action integrations.

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

2. In the upper-right corner of the Notification Policies page, click Create Notification Policy.

3. On the Create Notification Policy page, enter a notification policy name.

4. Configure a matching rule. A matching rule determines which alert events trigger this notification policy.

   1. Select a data source.

      • To process only alert events from a specific source, select that data source. ARMS processes alert events of the specified data source and sends alert notifications based on the matching rule.

      • To process all alert events regardless of source, select No Preset Source. ARMS processes all alert events and sends alert notifications based on the matching rule.

   2. Define one or more filter expressions using tags. Add custom tags or select from existing tags.

      Existing tags come from two sources:

      • Fields defined in alert rule expressions. For details, see Create an alert rule for a Prometheus instance.

      • Default tags provided by Application Real-Time Monitoring Service (ARMS). See the default tags reference below.

      Note: To require multiple conditions at the same time (AND logic), click + condition within the same matching rule. To trigger the policy when any one condition is met (OR logic), click + add rule to add a separate matching rule.

   3. Click Next.

5. Configure event grouping. Grouping controls how alert events are batched into notifications. Click Next.

   Option	Behavior
   No grouping	All alert events are sent to the contacts in a single alert notification.
   Group by field	Alert events that share the same field value are grouped into a single notification, reducing alert noise.

6. Configure notification objects.

   1. Click + Add Notification Object and select one or more recipients.

      

      Recipient type	Description
      Contact	An individual contact. Select a notification method: phone call, text message, or email.
      Contact group	A group of contacts. Select a notification method: phone call, text message, or email.
      Shift	An on-call schedule. Select a notification method: phone call, text message, or email.
      IM application	A messaging channel: DingTalk, Lark, or WeCom.
      Webhook	A custom webhook endpoint.

   2. Specify whether to send clearing notifications after an alert is resolved. When enabled, the alert status automatically changes to Resolved after all related events are handled, and the system sends a clearing notification to the configured recipients.

   3. Select a notification template to customize the alert message format. For details, see Configure a notification template and a webhook template.

   4. Set the time window during which alert notifications are sent.

   5. (Optional) Select a ticket system integration to automatically create tickets from alerts. For details, see Notification integrations.

   6. Click Next.

7. Configure repeat, escalation, and clearing behavior. This stage controls what happens after the first notification is sent. Click Next.

   Option	Behavior
   No repeat or escalation	Only one notification is sent before the alert is cleared.
   Repeat notifications	Notifications are resent at a configured interval until the alert is cleared.
   Escalation policy	Notifications are sent to additional recipients based on the escalation policy until the alert is cleared.
   Manual clearing	Alerts must be manually handled and cleared.

8. Configure action integrations. Select action integrations that take effect when alerts are triggered or cleared.

9. Click Save.

Manage notification policies

After creation, notification policies appear on the Notification Policies page.

Default tags reference

ARMS provides the following default tags for use in matching rule expressions.