Docs

Cloud Monitor

Alert templates

Creating an alert template

Creating an alert template

Alert templates save the alert rules of monitoring items for various cloud services, which help you quickly create alert policies.

Limits

Each root user can have up to 1,000 alert templates at the same time.

Each alert template can contain up to 100 alert policies.

Procedure

Log in to the Cloud Monitor console.

In the left navigation bar, click Alert Center > Alert Template.

Click the Alert Template tab and click Create alert template.

On the Create alert template page, specify the related parameters.

Parameter	Descriptions
Name	Specify a custom name for the alert template to identify the alert template. The name must be 1 to 128 characters in length. The name cannot start with a digit, a hyphen (-), or other special characters. The name can contain special characters. warning Alert notifications sent through SMS messages may fail to be delivered if some characters are used in the name. For more details, refer to Template review specifications.
Description	Specify a custom description for the alert template.
Alert object	Click Add alert object to specify an object to be monitored. Resource type: Specify the type of monitored cloud service. New dimension: Click New dimension to specify the resource subnamespace of the monitored cloud service. tip The alert template can be applied to multiple subnamespaces of multiple cloud services. Subnamespace: The console presets trigger conditions based on the resource subnamespaces to help you quickly configure alert policies. Select Use preset trigger conditions to automatically specify the Metric type and Trigger condition parameters, which can be modified, deleted, and added. If no preset trigger conditions are configured for a subnamespace, you cannot select Use preset trigger conditions. Rule name: Specify a custom name for the alert rule. The name must be 1 to 64 characters in length. The name cannot start with a digit, a hyphen (-), or other special characters. The name can contain special characters. Metric type: Select the metric type. Valid values: Single metric and Multiple metrics. 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. If a rule triggers both a threshold alert and a NoData alert at the same time, two notifications will be sent. For example, the trigger condition average disk utilization > 60%, lasting for 120 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 60% for consecutive 120 minutes, an alert will be triggered. Duration: The duration can be set to 1 cycle, 3 cycles, 5 cycles, 10 cycles, 15 cycles, 30 cycles, 60 cycles, or 120 cycles. Comparison operator: The comparison operator can be set to >, >=, <, <=, !=, =, Compare to Last Period Increase, Compare to Last Period Decrease, Compare to Last Period Increase or Decrease, Compare to The Same Period of Yesterday Increase, Compare to The Same Period of Yesterday Decrease, Compare to The Same Period of Yesterday Increase or Decrease, Compare to The Same Period of Last Week Increase, Compare to The Same Period of Last Week Decrease, or Compare to The Same Period of Last Week Increase or Decrease. Alert level: indicates the severity level of the alert. Valid values: Critical, Warning, Notification. You can select different thresholds for different alert levels under the same condition.
Mute For	After an alert policy is triggered, if the monitored resource continuously triggers alerts, the system will periodically send alert 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, 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. For threshold alerts, if the resource generates no alert for consecutive 5 minutes, the alert is cleared. For NoData alerts, if the resource reports data for consecutive 5 minutes, the alert is cleared. If you set the Notify Mode parameter to Rule, an alert recovery notification will be sent after the alerts of all resources are cleared. If you set the Notify Mode parameter to Rule and resource, an alert recovery notification will be sent after the alert of each resource is cleared.
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. tip You can configure 3 to 20 cycles. The default value is 10 cycles. Not all cloud service metrics support NoData alerts. NoData alerts can be configured only when the Subnamespace parameter in the Alert object section is set to Instance, and only one level of cloud service metrics exists for the resource. The options displayed in the console shall prevail. If a rule triggers both a threshold alert and a NoData alert at the same time, two notifications will be sent. NoData alert notifications will not be sent if the corresponding resource is deleted. For example, the Resources parameter is set to All in the Alert object section. If Resource A is deleted and no data is reported for consecutive n cycles, no NoData alert will be sent.

Click Create to complete the configuration.

Last updated: 2026.07.10 14:02:21