Use escalation and silence policies to centrally manage alert handling during scenarios such as version or feature upgrades, canary releases, and maintenance windows to prevent unnecessary alerts or alert storms. Escalation policies are often used with silence policies. For example, use a silence policy to suppress notifications and reduce noise during an upgrade.
Key rule: Silence policies take precedence over notification policies. Events are matched against silence policies first. If an event matches a silence policy, it is silenced and will not trigger a notification.
Escalation Policy
Log on to the Cloud Monitor 2.0 console, select the target workspace, and in the left-side navigation pane, choose .
Click Create Escalation Policy.
Basic Information:
Policy Name: Up to 128 characters.
Description: Up to 1024 characters.
Escalation Configuration: You can configure multiple escalation stages. Each stage includes:
Trigger Condition: Triggers N minutes after an alert occurs if it remains unacknowledged or unresolved.
Notification Recipient: Select the recipients to notify.
Effective Time: An escalation policy is typically active only during a specific time window. Click Modify Time to configure the schedule and set whether to send repeated notifications.
After you configure the policy, you can perform the following operations in the escalation policy list:
View the list: View columns such as Name, Description, Effective Scope (Number of Conditions/Expression), Schedule Type, Effective Time, Status, and Actions.
Edit: Modify settings such as the scope conditions and time window.
Enable/Disable: Use the toggle to activate or deactivate the policy.
Delete: Deletion is irreversible. Proceed with caution.
Silence Policy
Log on to the Cloud Monitor 2.0 console, select the target workspace, and in the left-side navigation pane, choose .
Click Create Silence Policy.
Basic Information:
Name: Up to 128 characters.
Description: Up to 1024 characters.
Effective Scope: Set the conditions under which the policy takes effect.
Schedule Type: Select One-time or Recurring and configure the time window.
After you configure the policy, you can perform the following operations in the silence policy list:
View the list: View columns such as Name, Description, Effective Scope (Number of Conditions/Expression), Schedule Type, Effective Time, Status, and Actions.
Edit: Modify settings such as the scope conditions and time window.
Enable/Disable: Use the toggle to activate or deactivate the policy.
Delete: Deletion is irreversible. Proceed with caution.
Configuration Examples
Example 1: One-time upgrade silence
Scenario: Upgrade the order-service from 01:00 to 03:00 on 2026-02-10 and silence the related alerts.
Effective Scope: "Service Name = order-service". You can add other conditions, such as "Environment = Production" or "Region = China (Hangzhou)".
Schedule Type: One-time (01:00–03:00).
Example 2: Canary Release with Composite Conditions
Scenario: You are upgrading Service A in the China (Hangzhou) region and Service B in the China (Beijing) region simultaneously, and you want to silence alerts for both upgrades.
Compound expression: (1 AND 2) OR (3 AND 4) (A combination of region and service name pairs).
Notes
To prevent notifications during an upgrade, use a silence policy. Ensure the silence window covers the entire upgrade period, preferably with a buffer before and after.
An event that matches any active silence policy will be silenced.