You can create CloudMonitor alert rules to monitor the usage and status of your Object Storage Service (OSS) resources. If resource metrics meet specific alert conditions, alerts are triggered and CloudMonitor sends alert notifications. This way, you can identify and handle the monitoring data exceptions at the earliest opportunity.
Create an alert rule
- Log on to the CloudMonitor console.
In the left-side navigation pane, choose Alerts > Alert Rules.
On the Alert Rules page, click Create Alert Rule.
In the Create Alert Rule panel, configure the parameters described in the following table.
Parameter
Description
Product
The name of the Alibaba Cloud service that you want to monitor by using CloudMonitor. Select Object Storage Service.
Resource Range
The range of the resources to which the alert rule is applied. Valid values:
All Resources: The alert rule applies to all OSS resources.
Application Groups: The alert rule applies to all resources in a specific application group of OSS.
Instances: The alert rule applies to specific OSS resources.
Rule Description
The condition content of the alert rule. An alert is triggered when the conditions are met. To specify the content of the alert rule, perform the following steps:
Click Add Rule.
In the Add Rule Description panel, specify the rule name, metric type, metric, threshold, and alert level.
ImportantIf you set the alert notification method to Email + Webhook, you are not charged.
Click OK.
Mute for
The interval at which CloudMonitor resends alert notifications before an alert is cleared. Valid values: 5 Minutes, 15 Minutes, 30 Minutes, 60 Minutes, 3 Hours, 6 Hours, 12 Hours, and 24 Hours.
An alert is triggered when the conditions of an alert rule are met. If the alert is triggered during the mute period, CloudMonitor does not resend alert notifications. If the alert is not cleared after the mute period elapses, CloudMonitor resends alert notifications.
Effective Period
The period of time during which the alert rule is effective. CloudMonitor monitors the specified resources and generates alerts only within the specified period.
Alert Contact Group
The alert contact group to which alert notifications are sent.
The alert notifications are sent to the alert contacts that belong to the selected alert contact group. An alert contact group can contain one or more alert contacts.
For more information about how to create an alert contact and an alert contact group, see Create an alert contact or alert contact group.
Alert Callback
The callback URL that can be accessed over the Internet. CloudMonitor sends HTTP POST requests to push alert notifications to the specified URL. Only the HTTP protocol is supported. For more information about how to configure an alert callback, see Use the alert callback feature to send notifications about threshold-triggered alerts.
NoteYou can click Advanced Settings to configure this parameter.
Auto Scaling
If you turn on Auto Scaling, the specified scaling rule is enabled when an alert is triggered based on the alert rule. If you turn on Auto Scaling, you must specify the Region, ESS Group, and ESS Rule parameters.
For information about how to create a scaling group, see Manage scaling groups.
For information about how to create a scaling rule, see Manage scaling rules.
NoteYou can click Advanced Settings to configure this parameter.
Log Service
If you turn on Log Service, an alert triggered based on the alert rule is written to the specified Logstore. If you turn on Log Service, you must specify the Region, ProjectName, and Logstore parameters.
For information about how to create a project and a Logstore, see Getting Started.
NoteYou can click Advanced Settings to configure this parameter.
Message Service - topic
If you turn on Message Service - topic, an alert triggered based on the alert rule is written to the specified topic in Message Service (MNS). If you turn on Message Service - topic, you must specify the Region and topicName parameters.
For information about how to create a topic, see Create a topic.
NoteYou can click Advanced Settings to configure this parameter.
Method to handle alerts when no monitoring data is found
Specify the method that is used to handle alerts if no monitoring data exists. Valid values:
Do not do anything (default)
Send alert notifications
Treated as normal
NoteYou can click Advanced Settings to configure this parameter.
Tag
Specify tags for the alert rule. A tag consists of a tag name and a tag value.
Click Confirm.
Manage alert rules
You can perform the following operations on alert rules:
Operation | Description |
If an existing alert rule cannot meet your metric monitoring requirements for an Alibaba Cloud service, you can modify the alert rule. | |
If you stop an Alibaba Cloud service for maintenance or upgrade, you can disable the alert rules that are associated with the service. This way, CloudMonitor does not send alert notifications for the alerts that are triggered by maintenance or upgrade operations on the service. | |
After you complete the maintenance or upgrade of a monitored Alibaba Cloud service, you can re-enable the associated alert rules that have been disabled during the maintenance or upgrade. | |
If you no longer need an alert rule, you can delete the alert rule. Important If you delete a bucket, the alert rules that are associated with the bucket are not deleted. You must manually delete the alert rules that you do not want to retain. | |
You can view the alert history and resources that triggered alerts of a specific alert rule. This way, you can identify and handle exceptions at the earliest opportunity. | |
Use the alert callback feature to send notifications about threshold-triggered alerts | Apart from emails and WebHook, CloudMonitor can also use the alert callback feature to integrate alert notifications into existing O&M systems or message notification systems. |
If an alert rule is triggered for multiple resources of the same Alibaba Cloud account within a specific cycle, CloudMonitor sends the first alert notification and merges subsequent alert notifications on a minute-by-minute basis. This reduces the consumption of CloudMonitor resources and prevents the interference of redundant information. |