CloudMonitor:Alert management

Prerequisites

The application is connected to Database Observability.

Alert rules

1. Log on to the Cloud Monitor 2.0 console. In the left navigation pane, choose Application Center > RDS Insights.

2. On the Database Insight 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.

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

   2. Monitoring Type: The monitoring type is set to RDS Insight by default.

   3. Set the following parameters.

      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.

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

   5. 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).

5. Click OK.

Alert history

For more information, see Alert history.