Escalation and silence policies
Use escalation and silence policies to centrally manage how alerts are handled during planned events such as version and feature upgrades, canary releases, and maintenance windows. This helps prevent unnecessary alerts and alert storms. An escalation policy is often used with a silence policy. If you want to suppress notifications for an alert event that occurs during an upgrade, use a silence policy.
Key rule: Silence policies are evaluated before notification policies. This means an alert event is first matched against silence policies. If a match is found, the event is silenced and is not processed for notifications.
Escalation policy
-
Log on to the CloudMonitor console, select the target workspace, and in the left-side navigation pane, choose .
-
Click Create Escalation Policy to configure an escalation policy.
-
Basic information:
-
Policy Name: A maximum of 128 characters.
-
Description: A maximum of 1,024 characters.
-
-
Escalation configuration: You can set up multiple escalation stages. Each stage includes:
-
Trigger: The policy is triggered if an alert remains unacknowledged or unresolved for N minutes after it occurs.
-
Notification Object: Select the notification object to receive alerts.
-
Effective Time: Escalation policies typically apply only during a specified window. Click Modification time to configure the schedule and specify whether to repeat notifications.
-
-
-
After the configuration is complete, the following operations are available on the escalation policy list page:
-
View list: Name, Description, Effective Scope (Number of conditions/expression), Effective Method, Effective Time, Status, and Actions.
-
Edit: Modify the scope conditions, time window, and other settings.
-
Enable/Disable: Use the switch to control whether the policy is active.
-
Delete: This operation cannot be undone. Proceed with caution.
-
Silence policy
-
Log on to the CloudMonitor console, select the target workspace, and in the left-side navigation pane, choose .
-
Click Create Silence Policy to configure a silence policy.
-
Basic information:
-
Name: A maximum of 128 characters.
-
Description: A maximum of 1,024 characters.
-
-
Effective Scope: Set the scope and conditions for the policy to take effect.
-
Effective method: Set the effective method to one-time or recurring, and set the time.
-
-
After the configuration is complete, the following operations are available on the silence policy list page:
-
View list: Name, Description, Effective Scope (Number of conditions/expression), Effective Method, Effective Time, Status, and Actions.
-
Edit: Modify the scope conditions, time window, and other settings.
-
Enable/Disable: Use the switch to control whether the policy is active.
-
Delete: This operation cannot be undone. Proceed with caution.
-
Configuration examples
Example 1: Silence for a one-time upgrade window
Use case: Silence alerts related to the order-service during an upgrade from 01:00 to 03:00 on February 10, 2026.
-
Effective Scope: Service Name = order-service (You can add other conditions, such as Environment = Production or Region = China (Hangzhou)).
-
Effective Method: One-time (01:00–03:00).
Example 2: Canary release with a compound condition
Use case: Manage alerts during a simultaneous upgrade of Service A in China (Hangzhou) and Service B in China (Beijing).
Compound Expression: (1 AND 2) OR (3 AND 4), which pairs a region with a service name.
Usage notes
-
If your goal is to suppress notifications during an upgrade, use a silence policy. Ensure the silence window covers the entire upgrade duration, preferably with a buffer before and after.
-
An event may match multiple policies. If it matches any silence policy, the event is silenced.