Docs

Cloud Monitor

Getting Started

Using Alert Center

Alert Center generates alerts for metrics. You can configure alert policies for key metrics of cloud products. When metric data changes or does not meet expectations, the system will immediately notify you about the exception, which enables you to handle the exception at the earliest opportunity.

Step 1: Create a contact

In the left navigation bar, click Notification > Contacts.

On the Contacts tab, click Create contact.

In the Create contacts dialog box, specify the Name, Email, and Phone parameters of the alert contact and then click Confirm.

After you configure the email address or phone number and create the contact, Cloud Monitor will send a verification message to the specified email address or phone number.

The following figure shows the verification message content sent to an email address. You need to click the URL to complete the verification.

Step 2: Create a contact group

When you create an alert policy, select the corresponding contact group to receive alert notifications through the contact group.

In the left navigation bar, click Notification > Contacts.

Click the Contact group tab.

On the Contact group tab, click Create contact group.

In the Create contact group dialog box, specify the Name, Description, and Select contacts parameters of the contact group and then click Confirm.

Step 3: Create a callback URL

In the left navigation bar, click Notification > Callback.

On the Callback address list page, click Create callback address.

On the Create callback address page, specify the following parameters and then click Confirm.

Parameter	Descriptions
Webhook name	Specify a custom name for the webhook to identify the callback URL. Duplicate names are not allowed.
Callback address type	Select the callback address type. Supported types include Lark, DingTalk, WeCom, and Generic Webhook.
Callback address	Enter a publicly accessible URL and then click Test to verify the callback URL. If the callback URL returns the HTTP status code 200, it indicates that the connectivity test is successful, and the webhook can receive alerts and event notifications. The connectivity test enforces a one query per second (QPS) limit.

Step 4: Create an alert policy

You can specify custom monitoring data thresholds, alert levels, the effective periods of alert policies, alert sending intervals, and notification methods. Flexible and diverse policies can meet your alert and monitoring requirements for different business scenarios.

In the left navigation bar, click Notification > Alert policy.

On the Alert policy page, click Create alert policy.

On the Create alert policy page, configure the details of the alert policy.

Basic information

Parameter
Descriptions
Name
Specify a custom name for the alert policy.
Description
Specify a custom description for the alert policy.

Alert object

Parameter	Descriptions
Resource type	Specify the type of monitored cloud service. Supported cloud service types displayed in the console shall prevail.
Subnamespace	Specify the resource subnamespace of the monitored cloud service.
Selection method	Manual selection: Manually select resources. Object Group: selects resources based on object groups. For specific operations, see Creating object groups. Resource name: selects resources based on resource names. Project: selects resources based on projects. For specific operations, see Managing projects. Label: selects resources based on labels. For specific operations, see Managing labels and resources.
Region	The region to which the monitored resource belongs.
Resource	Specify a resource range to which the alert policy applies, which means only resources within the resource range can be monitored. You can perform the following operations on resources: All: The alert policy is configured for all resources matching the specified resource type, region, and subnamespace within the current account. After selection, newly created resources that meet these conditions will be automatically added to the alert policy. Part: You need to manually select one or more resources. After selection, the alert policy is configured only for these resources.

tip

Available regions and subnamespaces vary based on the cloud service type. The options displayed in the console shall prevail.

Alert rules

Parameter	Descriptions
Use preset trigger conditions	The console presets trigger conditions based on the resource subnamespaces to help you quickly configure alert policies. If the Metric type parameter is set to Multi-metric, you can use the pre-configured trigger condition. Select Use preset trigger conditions to automatically specify the Metric type and Trigger condition parameters, which can be modified, deleted, and added. If no pre-configured trigger conditions are configured for a subnamespace, you cannot select Use preset trigger conditions.
Metric type	Select the metric type. Valid values: Single-metric and Multi-metric. If you need to monitor multiple metrics of a resource, you can select Multiple metrics.
Trigger condition	Configure the metrics, duration, statistic type, comparison operator, and threshold for the alert. If the monitored resource metric meets the trigger condition, the system will send an alert notification. If the Metric type parameter is set to Single metric, only one trigger condition can be set. If the Metric type parameter is set to Multiple metrics, one or more trigger conditions can be set. tip Take note of the following rules when you configure trigger conditions for multiple metrics: An alert can be triggered if any condition or all conditions are met. At least one and up to 10 trigger conditions can be configured. You cannot configure duplicate trigger conditions. For example, the trigger condition average disk utilization > 80%, lasting for 10 cycles (1 cycle = 1 minute) indicates the system checks the resource metric every 1 minute, and if the average disk utilization of a specific resource exceeds 80% for consecutive 10 cycles, an alert will be triggered.
Mute For	After an alert policy is triggered, if the monitored resource continuously triggers alerts, the system will periodically send alert notifications to prevent excessive notifications. You can set the alert sending cycle to 5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, or 24 hours. The default value is 5 minutes.
Notify mode	Rule: If any resource in the alert rule continuously exceeds the alert threshold during the alert sending cycle, only one alert notification is sent during the cycle. Rule and resource: If different resources in the alert rule continuously exceed the alert threshold during the alert sending cycle, alert notifications will be sent for each resource. If metrics do not recover after the alert sending cycle elapses, Cloud Monitor will send alert notifications again.
Alert recovery notification	A recovery notification is sent to users after the alert is cleared. The feature is enabled by default. warning An alert recovery notification is sent when the status of an alert policy returns to Normal and Cloud Monitor determines that an alert has recovered.
NoData alert	Configure the NoData alert. Configure a trigger condition. If no data is reported for the specified resource for consecutive n cycles, a NoData alert will be triggered. Configure the level of the NoData alert. Valid values: Critical, Warning, and Notice.

Advanced settings: Specify the project to which the alert policy belongs. The default project is selected by default.

Alert way

Parameter	Descriptions
Notification method	Select an alert notification channel. Manual selection: Manually configure a notification method of the alert policy. Notification policy: Specify a configured notification policy. For more details, refer to Creating notification policies.
Alert channel	Select one or more channels. Valid values: Email, Phone, SMS, and Alert callback. For the limits on receiving notifications by phone calls or SMS message, see Limit.
alert contact group	If you select one or more of the following options for Alert channel: Email, Phone, or SMS, the Alert contact group parameter will be displayed on the page. At least one contact group must be specified as the recipient of alert notifications. At most five contact groups can be specified as the recipients of alert notifications.
Webhook	If you set the Alert channel parameter to Alert callback, the Alert callback text box will be displayed on the page. You must specify a public URL as the webhook URL. If a resource subsequently triggers an alert policy, the system will send the alert details to this URL via a POST request, enabling you to perform in-depth data analysis. You can select created webhook URLs. Up to eight webhook URLs can be selected. You can enter only one webhook URL. We recommend that you prepare a server with the HTTP service enabled and accessible via the public network, and then specify the HTTP URL of the server as the callback URL. For more information about alert callbacks, see Alert callback usage. Alert webhooks can be associated with bots in Lark, DingTalk, and WeCom groups to automatically push alert notifications. For specific operations, see Receiving alert notifications by Lark group, Receiving alert notifications by DingTalk group, and Receiving alert notifications by WeCom group.

Last updated: 2026.07.15 14:24:29

Parameter	Descriptions
Name	Specify a custom name for the alert policy.
Description	Specify a custom description for the alert policy.