Alert rules

Prerequisites

• You have enabled the required observability monitoring services, such as Prometheus, Application Monitoring, and Log Service.

• You have created a notification contact.

Create an alert rule

1. Log in to the Cloud Monitor 2.0 console. In the left-side navigation pane, choose All Features > Alert Center.

2. On the Alert Center page, choose Alert Management > Alert Rule.

3. Click Create alert rules.

4. In the Create alert rules panel, configure the following parameters.

   1. Rule name: A name to identify the alert rule.

   2. Monitoring type: An object for the alert rule. Then, configure the parameters for the selected object. The following table describes the parameters.

      Parameter	Description
      Detection conditions	Set the conditions that trigger an alert. Duration: Set the duration of the alert detection period. Indicators Comparison Alert threshold: Critical: For major issues that affect core business availability and have a wide impact. Warning: For issues that might cause business errors or service impact. Info: For scenarios that require notification but have a low priority.
      Label	Custom key-value pairs used to categorize and filter alert rules. For example, env: production and team: sre.
      Annotation	Extended information for the alert rule. Use annotations to store long descriptions or links to runbooks. For example, description: High CPU utilization and runbook_url: https://wiki.xxx.com/runbook\.

   3. Notification Cofiguration

      • Notification recipient: The recipients to notify when an alert is triggered.

        • Contact: Individual contacts to notify.

        • Contact group: A group of contacts to notify.

        • DingTalk: Sends alerts to a DingTalk group chatbot.

        • WeCom: Sends alerts to a WeCom chatbot.

        • Lark: Sends alerts to a Lark chatbot.

        • Slack: Sends alerts by using Slack.

        • Custom webhook: Sends alerts by using a custom webhook.

      • Integrate with ARMS alert management: Integrates with Application Real-Time Monitoring Service (ARMS) to manage alert lifecycles.

        Note

        Alert events are sent to the ARMS Alert O&M center by default. Configure notifications there.

      • Action integration: The service to trigger for automated incident response, such as Log Service, lightweight message queues, Function Compute, and third-party services like PagerDuty and webhooks.

      • Notification silence period: The time to wait before resending a notification for an unresolved alert. Valid values: 1, 5, 10, 15, 30, and 50 minutes, and 1, 3, 6, 12, and 24 hours.

        Note

        Example: With Notification silence period set to 12 hours, Cloud Monitor resends the notification after 12 hours if the alert persists.

      • Effective period: The time window when the alert rule is active. Notifications are sent only during this period.

        Note

        • Alerts triggered outside the effective period are recorded in history but do not generate notifications.

        • The notification period can be set within a 24-hour range and can span across days, for example, from 23:00 to 01:00 on the next day.

Manage alert rules

1. The Alert Rules page lists all alert rules with the following information.

   Parameter	Description
   Alert status	The current status of the rule. Valid values: - Ok: No alert condition triggered. - Alarm: Alert condition triggered, alert active. - NoData: No monitoring data available.
   Rule name/ID	The display name and unique identifier (UUID) of the alert rule.
   Enabled status	Whether the rule is enabled. Enabled rules are evaluated at the configured interval; disabled rules are not.
   Service source	The service that the rule applies to.

2. You can search for alert rules using the following parameters:

   • Monitoring type

   • Rule name/ID

   • Alert status

   • Enabled status

   • More filters: Search by tag or notification contact.

If the resource scope of a system default alert rule is set to all resources, you cannot directly modify the resource scope to exclude specific instances after the rule is created.

To exclude specific resources, perform the following steps:

1. On the Alert rules page, find the target system default rule and click More > Duplicate in the Actions column.

2. In the Create alert rule dialog box, select the Prometheus instance or Aggregate view tab in the data source selector, and then select the specific resources that you want to monitor.

3. Click OK to save the new rule.

4. In the Actions column of the original system default rule, click More > Delete to delete the original rule, or turn off the Enabled status switch in the rule row to disable it.

   Note

   If you do not delete or disable the original rule, the same resource triggers two alerts when the threshold is reached.

• Edit: To edit an alert rule, select it and click edit in the actions column, modify the rule, and click OK.

• Enable/Disable: Toggle the switch in the enabled status column.

• Delete: Click delete in the actions column.

  Warning

  This action cannot be undone. Proceed with caution.