You can create threshold-triggered alert rules to manage and monitor the usage and operation of cloud service resources. When a metric value reaches the specified threshold, CloudMonitor sends an alert notification to you. In this way, you can be informed of exceptions and handle them efficiently.
CloudMonitor can send alert notifications by means of emails or DingTalk chatbots. If you need to receive alert notifications based on multiple methods, make sure that the specified information is correct when you configure alert contacts.
- Log on to the CloudMonitor console.
- In the left-side navigation pane, choose .
- On the Threshold Value Alarm tab of the Alarm Rules page, click Create Alarm Rule.
- On the Create Alarm Rule page, set the parameters in the Related Resource, Set Alarm Rules, and Notification
Parameter Description Product The name of the service monitored by CloudMonitor. Example: ECS. Resource Range The range of resources to which the alert rule is applied. Valid values: All Resources and Instances.
- All Resources: The alert rule is applied to all your instances of the specified service. Assume that you set the Resource Range parameter to All Resources and the alert threshold for CPU usage of ApsaraDB for MongoDB to 80%. CloudMonitor sends an alert notification when the CPU usage of an ApsaraDB for MongoDB instance exceeds 80%. If you set the Resource Range parameter to All Resources, the alert rule is applied to up to 1,000 instances. If the specified service has more than 1,000 instances, you may not receive alert notifications when the value of the specified metric reaches the threshold. We recommend that you add resources to service-specific application groups before you create alert rules.
- Instance: The alert rule is applied to a specific instance. Assume that you set the Resource Range parameter to Instances and the alert threshold for the CPU usage of an ECS instance to 80%. CloudMonitor sends an alert notification when the CPU usage of the ECS instance exceeds 80%.
Alarm Rule The name of the alert rule. Rule Description The content of the alert rule. This parameter defines the conditions that trigger an alert. For example, if you set the condition to that the average CPU usage in 5 minutes is greater than or equal to 90%, CloudMonitor checks whether the condition is met every 5 minutes.Take host monitoring as an example. A data point on the metric of a single host is reported at a 15-second interval. Therefore, 20 data points are reported in 5 minutes. CloudMonitor checks whether conditions are met based on the following rules:
- If the average value of the 20 data points on CPU usage reported in 5 minutes is greater than 90%, the average CPU usage in 5 minutes is greater than 90%.
- If the values of all the 20 data points on CPU usage reported in 5 minutes are greater than 90%, the CPU usage in 5 minutes is always greater than 90%.
- If the value of at least one of the 20 data points on CPU usage reported in 5 minutes is greater than 90%, the CPU usage in 5 minutes is greater than 90% for once.
- If the sum of the values of the 20 data points on outbound traffic over Internet reported in 5 minutes is greater than 50 MB, the total outbound traffic over Internet in 5 minutes is greater than 50 MB.
Mute for The interval of re-sending the notification for an alert before the alert is cleared. Effective Period The time period during which the alert rule is effective. CloudMonitor only checks whether monitoring data meets the alert rule during the effective period. Notification Contact The alert groups to which alert notifications are sent. Notification Methods
Email + DingTalk (Info)
Email Remark Optional. The custom additional information included the alert notification email. HTTP Callback The callback URL that can be accessed over the Internet. CloudMonitor pushes an alert notification to the specified callback URL by sending an HTTP Post request. Only the HTTP protocol is supported.
- Click Confirm.