ApsaraDB for MongoDB provides an instance status monitoring and alerting feature. This topic describes how to configure common metrics such as the usage of the disk space, input/output operations per second (IOPS), connections, and CPU.
- With the growth of data and development of business, more and more performance resources of ApsaraDB for MongoDB instances are consumed and even used up.
- In some scenarios, lots of performance resources of ApsaraDB for MongoDB instances are abnormally consumed. For example, a great number of slow queries increase the CPU usage and a large amount of data is written to fully occupy the disk space.
You can set alert rules for monitoring the key performance metrics of instances to help you detect abnormal data in a timely manner and quickly locate and handle faults.
- Log on to the ApsaraDB for MongoDB console.
- In the upper-left corner of the home page, select the region where the target instance is located.
- Locate the target instance and click its instance ID.
- In the left-side navigation pane, click Alarm Rules.
- Click Set Alarm Rule to jump to the CloudMonitor console.
- In the upper-right corner of the CloudMonitor console, click Create Alarm Rule.
- On the Create Alarm Rule page that appears, specify related resources.
Parameter Description Products The architecture of the instance.
Note If you select ApsaraDB for MongoDB-Cluster Instance, you need to select mongos nodes and shards to be monitored for Mongos and Shard, respectively.
- ApsaraDB for MongoDB-Instance Copy
- ApsaraDB for MongoDB-Cluster Instance
- ApsaraDB for MongoDB-Single node instance
- If you select All Resources, the alerting service sends an alert notification when any ApsaraDB for MongoDB instances match alert rules.
- If you select Instances, the alerting service sends an alert notification when any selected ApsaraDB for MongoDB instances match alert rules.
Regions The region where the instance is located. Instances The ID of the instance to be monitored. You can select multiple instance IDs.
- Set alert rules. You need to set the disk space usage first, and then click Add Alarm Rule.
- For example, if you set Rule Describe to Disk Usage 5mins Average >= 80%, the alerting service checks the disk space usage every 5 minutes to detect whether the average disk space usage in the last 5 minutes is greater than or equal to 80%. You can adjust each alert threshold based on your business scenarios.
- If you select AnyRole for Role, the alerting service monitors all primary and secondary nodes for each instance.
- Repeat the last step to set alert rules for the usage of the IOPS, connections, and CPU.
- Set other parameters for alert rules.
Parameter Description Mute for The interval at which the alerting service sends an alert notification repeatedly if an alert is not cleared. Effective Period The period during which alert rules take effect.
- Configure notification methods.
Parameter Description Notification Contact The contacts or contact group to which the alerting service sends an alert notification. For more information, see manage alert contacts and alert contact groups. Notification Methods The notification methods corresponding to the alert severity, which can be Critical, Warning, or Info.
- Critical: Email + DingTalk
- Warning: Email + DingTalk
- Info: Email + DingTalk
Email Subject The subject of the alert notification email. You can customize an email subject. The default email subject is as follows: Product + Metric + Instance ID. Email Remark The custom additional information of the alert notification email. After you enter email remarks, the alerting service sends an alert notification email that contains your custom remarks. HTTP CallBack For more information, see use alarm callback.
- Click Confirm. Alert rules automatically take effect.