ApsaraDB for MongoDB:Configure alert rules for ApsaraDB for MongoDB

Background

• As your data volume and business grow, the resource usage of your ApsaraDB for MongoDB instance may increase until resources are exhausted.

• In some scenarios, certain operations can consume instance resources at an abnormally high rate. For example, a high volume of slow queries can increase CPU utilization, or large-scale data writes can rapidly consume disk space.

  Important

  Insufficient disk space locks the instance.

By creating alert rules for key performance indicators (KPIs), you can receive immediate notifications about anomalies, helping you quickly identify and resolve issues.

Procedure

1. Log on to the ApsaraDB for MongoDB console.

2. In the upper-left corner of the page, select the resource group and region of your instance.

3. In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances, depending on your instance architecture.

4. Find the target instance and click its ID, or click Manage in the Actions column.

5. In the left-side navigation pane, click Alert Rules.

6. Click Set Alert Rule. You are redirected to the CloudMonitor console.

7. On the Alert Rules page of the CloudMonitor console, click Create Alert Rule in the upper-left corner.

8. In the Create Alert Rule panel, configure the parameters for the alert rule.

   Parameter	Description
   Service	The Alibaba Cloud service to monitor. Examples include: ApsaraDB for MongoDB - Replica Set ApsaraDB for MongoDB - Sharded Cluster ApsaraDB for MongoDB - Standalone Instance
   Resource Scope	The resources covered by the alert rule. Valid values: All Resources: The alert rule applies to all resources of the specified cloud service, including newly added ones. Application Groups: The alert rule applies to all resources within a specified application group, including newly added ones. Instance: The alert rule applies only to specific resources of the cloud service.
   Rule Description	The conditions that trigger the alert. To define the rule, follow these steps: Click Add Rule. In the Add Rule Description panel, configure the parameters for the rule, such as the rule name, metric type, monitoring metric, threshold, and alert level. Click Determine. Note For information about how to set complex alert conditions, see Alert rule expressions.
   Mute Period	The period to wait before resending a notification for an unresolved alert. Valid values: 5 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, and 24 hours. CloudMonitor sends a notification when a metric first crosses the alert threshold. If the metric continues to exceed the threshold, CloudMonitor will not send another notification during the mute period. If the alert is still active after the mute period ends, CloudMonitor sends a new notification. For example, if you set Mute Period to 12 Hours, and an alert is not resolved, CloudMonitor will send another notification after 12 hours.
   Effective Period	The time period during which the alert rule is active. CloudMonitor checks for alerts only within this period.
   Alarm Contact Group	The contact group that receives alert notifications. CloudMonitor sends notifications for an application group to the alert contacts in this group. An alert contact group can contain one or more alert contacts. For information about how to create alert contacts and alert contact groups, see Create an alert contact or an alert contact group.
   Tag	Key-value pairs used to categorize the alert rule.

   For information about advanced settings, see Create an alert rule.

9. After you complete the configuration, click Confirm. The alert rule takes effect immediately.