Cloud Monitor:Create and manage alert rules

Prerequisites

• You have created the objects you want to monitor by type.

• You have created the notification objects for the alerts.

Create an alert rule

1. Log on to the Cloud Monitor 2.0 console. In the left navigation pane, choose Application Center > 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, configure the following parameters:

   • Rule Name: Enter a rule name.

   • Monitoring Type: Select a monitoring type.

     • 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.
       Method for Defining Detection Conditions	Custom PromQL: Define a custom PromQL query syntax. For more information, see PromQL function usage examples.
       	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 value. 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: Info
       Duration	Set the duration for the alert.
       Alert Check Interval	Set the time for the alert check interval.
       Check After Data Completion	Select a check method.
       Content	Customize the alert message.

     • 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 metric group for the application.
       API Name	Select a matching method for the API, such as Traverse, Equal to, Not Equal to, Regex Match, Regex Mismatch, or None.
       API Call Type
       Detection Condition Method	Single Condition: Set the Last N Minutes, call type, and calculation method, then select a comparison operator. Set the values for different severity levels: Critical, Error, Warning, and Info. PromQL Preview: Preview the PromQL statement for the predefined metric. Multiple Conditions: Alert Trigger Rule: Select how the conditions trigger the alert rule. The alert can be triggered if Any Condition Is Met or All Conditions Are Met. Detection Condition 1: For parameter settings, see the "Single Condition" section. Add Condition: Add multiple sets of detection conditions as needed. Severity Level: Select a severity level as needed. Valid values: P1: Critical, P2: Error, P3: Warning, and P4: Info.
       Alert Check Interval	Set the time for the alert check interval.
       Detection Judgment	Preview the content of the custom detection judgment.

     • RUM

       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. Valid values: Exception Monitoring, Stuttering Monitoring, Resource Monitoring, and Page Monitoring.
       Filter Condition	Different predefined parameters are available based on the selected metric group. Select a method to match the input value. Valid values: Traverse, Equal to, Not Equal to, Contain, Not Contain, Regex Match, Regex Mismatch, and None.
       Detection Condition Method	For details, see the Application Monitoring settings.
       Alert Check Interval	Set the time for the alert check interval.
       Detection Judgment	Preview the content of the custom detection judgment.

     • 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. Valid values: Exception Monitoring, Stuttering Monitoring, Resource Monitoring, and Page Monitoring.
       Filter Condition	Different predefined parameters are available based on the selected metric group. Select a method to match the input value. Valid values: Traverse, Equal to, Not Equal to, Contain, Not Contain, Regex Match, Regex Mismatch, and None.
       Detection Condition Method	For more information, see the settings for Application Monitoring.
       Alert Check Interval	Set the time for the alert check interval.
       Detection Judgment	Preview the content of the custom detection judgment.

     • Basic Cloud Monitor

       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. Valid values: All Resources, Application Group, and Instance.
       Metric Type	Set the metric method for the alert rule as needed. Simple Metric: Set a metric, then set its threshold and alert level (Critical, Warning, and Info). Set the interval and threshold for each level. Combined Metric: Select different alert levels and combine multiple metrics as needed. Multi-metric Alert: Add multiple metrics and set threshold conditions. Note For a multi-metric alert rule, the target resource must provide data for all specified metrics, and the alert can be triggered only when the rule's conditions are met. For example, a rule that includes a public network metric will not trigger on an ECS host that lacks a public IP address, because the host cannot report data for that metric. Multi-metric Relationship: After adding metrics with different conditions, you can set a logical operator. For example, trigger an alert when all conditions are met or when any condition is met. Expression: Select an alert level, and set Alert Expression and Alert Threshold Trigger Count.
       No-Data Behavior	Choose how the system reacts when no metric data is reported. Ignore: Take no action. Send No-Data Alert: Trigger a new alert with no data. Resolve Alert: Automatically close any alert associated with the metric.

     • Hybrid Cloud Monitoring: Select a custom metric repository. For other configuration parameters, see the "Managed Service for Prometheus" section in this topic.

     • Synthetic Monitoring: For configuration parameters, see the "Managed Service for Prometheus" section in this topic.

     • Container Insight/ECS Insight/RDS Insight/AI Infra Service Insight/Redis Insight: For configuration parameters, see the "Managed Service for Prometheus" section in this topic.

     • Log Audit

       Parameter	Description
       Select Template	Operation Audit Host Audit
       Query And Statistics	Single Query: Perform a single query by setting log-related information. Set Operation: Add multiple resource groups.
       Detection Judgment	Add multiple conditions, and set the data matching method and severity level.
       Severity Level	Valid values: P1: Critical, P2: Error, P3: Warning, and P4: Info.
       Consecutive Occurrences	Set the number of consecutive times the condition must be met to trigger an alert.
       Alert Check Interval	Set a custom time for the alert check interval.

     • Simple Log Service: For configuration parameters, see the "Log Audit" section in this topic.

   • Alert Information:

     • Content: Customize the alert message.

     • Tags and Annotations: Set tags and annotations for the alert rule. Each tag consists of a tag name and a tag value.

   • Alert Notifications:

     • Notification Objects: Select one or more notification objects for receiving alerts. Valid values: Contact, Contact Group, DingTalk, WeCom, Lark, Slack, and Custom Webhook.

     • Integrate Into ARMS Alert Management: Select Yes or No.

       Note

       By default, alert events are sent to ARMS Operation Center. To configure alert notifications, go to the ARMS Operation Center.

     • Action Integration: Select a cloud product or third-party service to handle tasks after an alert is triggered. Examples include Simple Log Service, SMQ, Function Compute, and third-party services such as PagerDuty and Webhook.

     • Silence Period: The interval at which an alert notification is resent if the alert is not resolved. Valid values: 1, 5, 10, 15, 30, and 50 minutes, and 1, 3, 6, 12, and 24 hours.

       Note

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

     • Effective Period: Set the time window when the alert rule can send notifications.

       Note

       • Alerts triggered outside this period are silenced, but the events are still recorded in the alert history.

       • The time window can span across days (for example, 23:00 to 01:00).

Manage alert rules

On the Alert Rules page, you can perform the following actions on the alert rules:

• Search: Filter alert rules by type, or search for a specific alert rule using the following parameters:

  • Monitoring Type

  • Rule Name

  • Rule ID

  • Alert Status

  • Enabled/Disabled

  Alternatively, click More Filters on the right, and search by Add Tag and Add Notification Object.

• Edit: Click Edit in the Actions column. In the dialog box that appears, edit the rule information and click OK.

• Delete: Choose > Delete in the Actions column.