Cloud Monitor:Notification policy

Create a notification policy

1. Log on to the CloudMonitor 2.0 console, select the target workspace, and from the left-side navigation pane, choose alert center > notification management > notification policy.

2. Click Create Notification Policy and configure the following settings:

   • Basic Information:

     • Name: The name of the notification policy. It must not exceed 120 characters.

     • Description: A description of the notification policy. It must not exceed 120 characters.

   • Routing Rule: Routing rules define how events are routed for notification. The system evaluates these rules sequentially and stops after the first match.

     • Deduplication and noise reduction: To reduce redundant notifications, configure grouping fields to aggregate similar events. You can select up to five grouping fields. In addition to common grouping fields, you can also specify custom fields based on the event data. By default, labels._cms_rule_id (alert rule ID) and resource.entity.entity_id (resource entity ID) are used.

     • Routing rule configuration: Each notification policy can have multiple routing rules. Click Add Routing Rule to add a new rule.

       • Routing condition: Define custom matching conditions. You can add multiple conditions.

       • Notification object: Specify the recipients for the notification. You can add multiple recipients. For 'contact', 'contact group', or 'on-call schedule' objects, you must also select a notification method, such as a phone call, SMS, or email. Other object types do not require this.

       • Effective period: By default, the rule is effective 24/7. Click Modify Time to specify a custom effective period.

   • Notification Rule (Optional): Configure advanced notification rules, including notification templates, recovery notifications, auto-recovery, repeated notifications, and action integrations.

     • Notification template settings: Configure a notification template for each channel type.

     • Recovery notification:

       Option	Description
       Send recovery notification	Sends a notification when an alert is resolved.
       Do not send recovery notification	Does not send a notification when an alert is resolved (default).

     • Auto-recovery:

       Option	Description
       Alerts do not recover automatically	If an alert expires and the underlying issue is not resolved, the alert remains active.
       Alerts recover automatically after N minutes/seconds	The alert recovers automatically when it expires, even if the underlying issue is not resolved.

     • Repeated notification:

       Option	Description
       No repeat notification is required	Sends only one notification while the alert is active.
       If an alert is not recovered, send a repeat notification every N minutes/seconds	Sends notifications periodically until the alert is recovered.

     • Action integration: Configure action integrations to run automatically when an alert is triggered or resolved.

       Parameter	Description
       Trigger action integration upon firing	Runs the specified action integration when an alert is triggered.
       Trigger action integration upon recovery	Runs the specified action integration when an alert is resolved.

     • Escalation policy: Select a pre-configured escalation policy. If an alert is not handled within a specified time, it is automatically escalated.

3. After you complete the configuration, click OK.

4. The notification policy list page displays all created policies with the following information:

   Field	Description
   Name	The name of the notification policy.
   Description	The description of the notification policy.
   Grouping condition	The grouping fields used for event deduplication and noise reduction.
   Notification mode	Displays the trigger method and mute time. For example, "Trigger immediately, no further notifications for 5 minutes."
   Number of routing rules	The number of routing rules in the policy.
   Number of custom notification templates	The number of custom notification templates configured in the policy.
   Source	The source of the policy, such as Managed Service for Prometheus, ARMS, or CloudMonitor.
   Last modified time	The time when the policy was last modified.
   Status	The status of the policy (enabled or disabled).

5. The following operations are available on the list page:

   • Create Notification Policy: Click the Create Notification Policy button to open the policy creation page.

   • Search: Supports fuzzy search by policy name.

   • Filter by Status: Filter policies by their enabled or disabled status.

   • Sort: Sort by last modified time or status.

   • Edit: Click the Edit button to modify the policy configuration.

   • Delete: Click the Delete button to delete the policy. Policies synchronized from ARMS or CloudMonitor cannot be deleted.

   • Enable/Disable: Use the toggle to enable or disable the policy.

Event matching process

1. When a policy receives an event, it first applies deduplication and noise reduction based on the configured grouping fields.

2. The system then matches the event against the routing rules in sequential order.

3. For each routing rule, the system checks if the event meets the routing conditions and is within the effective period.

4. The first matching routing rule is applied, and all subsequent rules are ignored.

5. A notification is sent to the notification objects specified in the matched rule.

6. Recovery notifications, auto-recovery, and repeated notifications are handled based on the configured notification rules.