Cloud Monitor:Create and manage alert rules

Prerequisites

• You have created the monitored objects for which you want to create alerts, based on the monitoring type.

• You have created the notification recipients for the alerts.

Create an alert rule

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

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

3. On the Alert Rules page, click Create Alert Rule.

4. In the Create Alert Rule panel, set the parameters for the alert rule.

   1. Rule Name: Enter a custom name for the alert rule.

   2. Monitoring Type: Select the desired monitoring type for the alert rule.

      • Managed Service for Prometheus

        Parameter	Description
        Data Source Type	The data source of the target monitoring type.
        Region	The region of the data source.
        Prometheus Instance	Set the alert rule based on the selected target instance.
        Detection Condition Definition Method	Custom PromQL: You can Customize PromQL query syntax based on your requirements. For more information, see PromQL function usage examples.
        	Configure Based on Predefined Metrics: Metric Group: Select a metric group. Metric: Select a metric. Detection Condition: Set the detection condition by specifying a comparison operator and a count. PromQL Preview: Preview the PromQL statement for the predefined metric.
        Severity Level	Set the severity level for the alert rule. P1: Critical P2: Error P3: Warning P4: Normal
        Duration	Set the duration for the alert.
        Alert Detection Period	Set the time for the alert detection period.
        Detect After Data Is Complete	Select a detection method.
        Content	Use Go template syntax to customize the content of the alert message. Example: Namespace: {{$labels.namespace}} / Pod: {{$labels.pod_name}} / Container: {{$labels.container}} CPU usage {{$labels.metrics_params_opt_label_value}} {{$labels.metrics_params_value}}%, Current value {{ printf "%.2f" $value }}%

      • Application Monitoring

        Parameter	Description
        Data Source Type	The data source type of the target monitoring type.
        Region	The region of the data source.
        Application	Select the application instance for which to set the alert rule.
        Metric Group	Select a group for the application metrics.
        API Name	Select a matching method for the API, such as All, Equals, Not Equals, Regex Match, Regex Not Match, or No Dimension.
        API Call Type
        Detection Condition Method	Single Condition: Set Last N Minutes, the call type, and the calculation method, and select a comparison operator. Set the values for different levels: Critical, Error, Warning, and Normal. PromQL Preview: Preview the PromQL statement for the predefined metric. Multiple Conditions: Multiple Alert Trigger Rule: Select the condition for triggering the alert rule. You can choose Any condition is met or All conditions are met. Detection Condition 1: Refer to the parameter settings for a single condition. Add Detection Condition: Add more detection conditions as needed. Severity Level: Select a severity level as needed, including P1: Critical, P2: Error, P3: Warning, and P4: Normal.
        Alert Detection Period	Set the time for the alert detection period.
        Detection Judgment Description	Preview the content of the custom detection judgment.

      • Real User Monitoring

        Parameter	Description
        Data Source Type	The data source type of the target monitoring type.
        Region	The region of the data source.
        Application	Select the application instance for which to set the alert rule.
        Metric Group	Select an application metric group, including Exception Monitoring, Unresponsiveness Monitoring, Resource Monitoring, and Page Monitoring.
        Filter Condition	Based on the selected Metric Group, different predefined parameters are available. You can select a matching method for the input value, such as All, Equals, Not Equals, Contains, Does Not Contain, Regex Match, Regex Not Match, or No Dimension.
        Detection Condition Method	Refer to Application Monitoring above.
        Alert Detection Period	Set the time for the alert detection period.
        Detection Judgment Description	Preview the content of the custom detection judgment.

      • Large Language Model (LLM) Observability

        Parameter	Description
        Data Source Type	Prometheus Log
        Region	The region of the data source.
        Application	Select the application instance for which to set the alert rule.
        Metric Group	Select an application metric group, including Exception Monitoring, Unresponsiveness Monitoring, Resource Monitoring, and Page Monitoring.
        Filter Condition	Based on the selected Metric Group, different predefined parameters are available. You can select a matching method for the input value, such as All, Equals, Not Equals, Contains, Does Not Contain, Regex Match, Regex Not Match, or No Dimension.
        Detection Condition Method	Refer to Application Monitoring above.
        Alert Detection Period	Set the time for the alert detection period.
        Detection Judgment Description	Preview the content of the custom detection judgment.

      • CloudMonitor Basic

        Parameter	Description
        Product	Select the target cloud product for which to create the alert rule.
        Resource Scope	Set the resource scope for the selected cloud product, including All Resources, Application Group, and Instance.
        Metric Type	Set the metric type for the alert rule as needed. Simple Metric: Set the Metric, then set its threshold and alert level, including Critical, Warning, and Normal. Set the period and threshold for each level. Combined Metric: Select different alert levels and combine multiple metrics. Multi-metric Alert Description: Add multiple different metrics and set threshold conditions. Note If you set a multi-metric alert rule, the target resource must have data for each metric. The alert is triggered only after the conditions are met. For example, if a multi-metric alert rule includes a metric for the public network, but the ECS host is not configured with a public IP address, the alert will not be triggered. Multi-metric Relationship: After adding metrics with different conditions, you can set a logical operator, such as triggering an alert when all conditions are met or when any one condition is met. Expression: First, select the Alert Level. Then, configure the Alert Expression and the Number of Times the Alert Threshold Is Triggered.
        No Data Processing Method	Select a method for handling no data. Do not process Send no-data alert Consider as recovered

      • Hybrid Cloud Monitoring: Select a custom Metric Repository. For subsequent configurations, refer to the parameter descriptions for the Managed Service for Prometheus monitoring type in this document.

      • Synthetic Monitoring: Refer to the parameter descriptions for the Managed Service for Prometheus monitoring type in this document.

      • Container Insight, ECS Insight, RDS Insight, AI Infra Service Insight, or Redis Insight: Refer to the parameter descriptions for the Managed Service for Prometheus monitoring type in this document.

      • Log Auditing

        Parameter	Description
        Select Template	ActionTrail: Select an ActionTrail template as needed. Host Auditing: Select a host auditing template as needed.
        Query Statistics	Single Query: Perform a single query by setting log-related information. Set Operation: Set the method for the set operation. You can add multiple resource groups.
        Detection Judgment	Add multiple conditions as needed. Set the data matching method and severity level.
        Severity Level	Select an alert level as needed, including Critical, Error, Warning, and Normal.
        Consecutive Occurrences	Set the number of consecutive times the condition must be met to trigger an alert.
        Alert Detection Period	Set a custom period for alert detection.

      • Simple Log Service: Refer to the parameter descriptions for the Log Auditing monitoring type in this document.

   3. Set the Alert Information.

      1. Content: Customize the alert information.

      2. Labels and Annotations: Set the labels and annotations for the alert rule. Each label or annotation consists of a tag name and a tag value.

   4. Set the Alert Notification.

      1. Notification Recipient: Select one or more notification recipients, such as Contact, Contact Group, DingTalk, WeCom, Lark, Slack, or Custom Webhook, to receive alert information when an alert is triggered.

      2. Integrate into ARMS Alert Management: Select Yes or No.

         Note

         Alert events are sent to the ARMS Operation Center by default. You can configure alert notifications in the ARMS Operation Center.

      3. Action Integration: Select specific cloud products or third-party services to handle subsequent alert transactions, such as Simple Log Service, a lightweight message queue, Function Compute, and third-party services such as PagerDuty and Webhook.

      4. Mute For: The interval for resending an alert notification if the alert is not resolved. Valid values are 1, 5, 10, 15, 30, and 50 minutes, and 1, 3, 6, 12, and 24 hours.

         Note

         For example, if you set Mute For to 12 hours, Cloud Monitor resends the alert notification after 12 hours if the alert is not resolved.

      5. Effective Period: The period during which the alert rule is active. Alert notifications are sent only during the effective period.

         Note

         • If an alert rule is outside its effective period, alert notifications are not sent. However, the alert is still recorded in the alert history.

         • The effective period can be set within a 24-hour period and can span across days. For example, you can set the period from 23:00 to 01:00 the next day.

Manage alert rules

On the Alert Rules page, you can search for, edit, and delete alert rules:

• Search: Filter the list of alert rules using the following parameters:

  • Monitoring Type

  • Rule Name

  • Rule ID

  • Alert Status

  • Enabled/Disabled

• More Filters: Click More Filters. You can also search using the Add Tag and Add Notification Recipient filters.

• Edit: Find the alert rule that you want to edit, click Edit in the Actions column, modify the information in the dialog box, and then click OK.

• Delete: Find the alert rule that you want to delete, and in the Actions column, click Delete.