Docs

Observability Platform

Notification settings

Creating notification policies

A notification policy defines the recipients, delivery channels, and content display format for alert notifications when alerts of different levels are triggered or resolved. This topic describes how to create an alert notification policy.

Prerequisites

You have selected an appropriate notification method based on the actual scenario. Supported notification methods vary by cloud service. For more details, see the descriptions of notification methods in Alert Center overview.

Create notification objects based on the selected notification method, such as contacts, contact groups, callback addresses, and on-call schedules. For more information, see Notification objects and Creating on-call schedules.

Create a notification template based on the selected notification method, such as notification templates for phone calls, email, Feishu bot, DingTalk, and a general callback address. For more details, see Creating notification templates.

Limits

You can create up to 1,000 notification policies.

You can add up to 10 contacts, 10 contact groups, 10 on-call schedules, and 10 webhook URLs for each notification policy.

You can add up to 10 orchestration plans, 10 message queues, and 10 log services.

Procedure

In the left navigation pane, select "Alert Center -> Notification configuration" to go to the "Notification configuration" page.

Select the Notification Policy tab, click Create notification policy, and configure the notification policy parameters as needed.

Parameter	Description
Policy name	Specify a name for the notification policy as a unique identifier. Duplicate names are not allowed.
Effective time	The effective time of the notification policy, which can be configured as needed.
Aggregate by contacts	This feature is disabled by default. When enabled, it aggregates alert events by contact before sending notifications. This significantly reduces the number of notifications and is suitable for low-priority, high-volume alert events. warning Because aggregation is based on a time window, notification delivery may be delayed. The actual delay depends on the configured time window. Aggregated alert events are not sent to contacts specified in alert escalation. Supported notification channels for aggregated alert events include phone calls, SMS, email, Feishu group bots, Feishu application bots, DingTalk, WeCom, and Slack. Aggregation pattern: Specifies how notifications are sent after "Aggregate by contacts" is enabled. "Send aggregate alert events only" means that only notifications generated from aggregated alert events are sent; the original alert event notifications are not sent. "Both alert and aggregate alert events are sent" means that both the original alert event notifications and notifications generated from aggregated alert events are sent. Time window: Specifies the time period for aggregating alert events. For example, a value of 10 minutes means that eligible alert events occurring within a 10-minute period are aggregated, and a single notification is sent to each specified contact. Aggregate alert event level: Specifies the levels of alert events to aggregate. You can select specific levels. If this parameter is left empty or all levels are selected, alert events from all levels are aggregated. Send contacts: Specifies the contacts who receive notifications for aggregated alert events. Specify the contacts to receive aggregated event notifications by selecting alert event levels. If this parameter is left empty or set to "All", aggregated notifications are sent to the contacts associated with all alert event levels.
Alert level configuration	The configuration methods of alert levels. Hierarchical configuration: Configure different notifications for alerts of different severity levels. For example, specify phone and Feishu group bot as the notification methods for alerts of the "Critical" and "Notice" levels, respectively. Overall configuration: Unified configuration settings regardless of alert severity levels.
Alert level	This parameter is required when you set the parameter Alert level configuration to hierarchical configuration. Currently, four alert levels are available: Critical, Warning, Notice, and Recovery. You can select alert levels as needed.
Notification methods	Select the alert notification methods and configure the corresponding parameters, such as notification object, Webhook, and notification template. tip Supported notification methods vary by cloud service. For more details, see the descriptions of notification methods in Alert Center overview.
		When the notification method is set to "Phone", "SMS", or "Email", configure the following parameters: warning For the limits on receiving notifications by phone calls or SMS message, see Limit. Notification object: the recipients of notification messages. Available options include contact group, contact, and on-call schedule. Multiple selections are supported. Notification template: the display style of notification messages, which corresponds to the notification method. For example, when you select "Phone" as the notification method, you also need to configure a phone notification template.
		When you select Feishu group bot, Feishu application bot, DingTalk, WeCom, Slack, or general callback address as the notification method, you need to configure the following parameters: Notification object: The recipients of notification messages. Available options include contact group, contact, and on-call schedule. Multiple selections are supported. Webhook: The callback address to which notification messages are delivered for the target application, which corresponds to the notification method. For example, when you select Feishu group bot as the notification method, you need to configure the callback address that supports the Feishu group bot at the same time. tip When alert notifications are pushed to a specified URL via HTTP or HTTPS POST requests, you need to add the egress IP addresses used by the general callback address to the firewall allowlist. After you receive an alert notification, you can take the corresponding measures based on the notification content. For more information about alert webhook URLs, refer to Alert webhook usage. Notification template: the display style of notification messages, which corresponds to the notification method. For example, when you select Feishu group bot as the notification method, you need to configure a Feishu group bot notification template. Mention contacts: disabled by default. This configuration is supported for notification methods, including Feishu group bot, Feishu application bot, DingTalk, and WeCom. When this configuration is enabled, the selected contacts, or the contacts in the selected contact groups or on-call schedules, are also mentioned when an alert message is received. Expedite contacts: disabled by default. This configuration is available when the notification method is set to Feishu application bot. When this configuration is enabled, urgent notifications are also sent to the selected contacts or the contacts in the selected contact groups or on-call schedules when an alert message is received. warning When you enable "Yes @contacts" or "Expedited contacts" in a notification policy, make sure that the selected contacts have the required information configured. Otherwise, the features cannot work properly. For example: Feishu group robots and Feishu application robots identify contacts through the "Feishu username" associated with the target contact. DingTalk identifies contacts through the "Mobile phone number" associated with the target contact. WeCom identifies contacts through the "WeCom account" associated with the target contact.
		When the notification method is set to "Orchestration", configure the following parameters: Notification object: the recipients of notification messages. Available options include contact group, contact, and on-call schedule. Multiple selections are supported. Orchestration plan: Select an appropriate orchestration plan based on your actual needs. For orchestration plan details and creation instructions, see Creating orchestration plans.
		When the notification method is set to "Message queue", configure the following parameters: Notification object: the recipients of notification messages. Available options include contact group, contact, and on-call schedule. Multiple selections are supported. Message queue for Kafka: Select an appropriate Kafka message queue based on your actual needs. For Kafka message queue details and instance creation instructions, see Creating topics.
		When the notification method is set to "Log service", configure the following parameters: Notification object: the recipients of notification messages. Available options include contact group, contact, and on-call schedule. Multiple selections are supported. Log service: Select an appropriate log service based on your actual needs. For log service details and creation instructions, see Log topics.
Alert upgrade	When an alert of the "Critical" level receives no response for a long time, it is sent to a new channel or contact. This feature is disabled by default. You can configure it as needed. warning The alert escalation feature applies only to alerts of the "Critical" level. Trigger condition: Configure the conditions that trigger alert escalation. For example, if an alert is sent more than N times without a response and remains unanswered for more than M minutes within the time window for statistics, the alert is escalated to level X. Notification method: Configure notification methods for alert escalation. We recommend using the methods with higher notification levels, such as phone calls, @mentions of contacts in Feishu or DingTalk, or urgent mentions of contacts via Feishu application bot messages. Notification object: Configure the recipients for alert escalation. We recommend configuring higher-priority contacts, contact groups, or on-call schedules.

What to do next

You can use the created notification policies for each product in alert tasks or alert policies. When an alert is triggered, notification messages are sent to the contacts in the display style specified by the notification policy. For configuration examples of alert tasks or alert rules, see Creating Cloud Monitor alert rules, Creating cloud service event rules, and Creating Server-side Monitoring alert tasks.

For the management operations supported for notification policies, see Managing notification policies.

Last updated: 2026.09.07 19:40:06