You can set an alarm rule for a specific Tencent Cloud product through a trigger template and then reuse the alarm rule to set alarm policies for other products, eliminating the need to set the same alarm rule repeatedly. When using a trigger template to set triggers for an alarm policy, you can edit the template and then apply it to the corresponding alarm policy group. This allows you to quickly modify alarm policies and rules in a unified manner, improving OPS efficiency. This document describes how to configure a trigger template.
An alarm trigger is a semantic condition consisting of metric, comparison, threshold, statistical period, and duration. For example, if the metric is CPU utilization, the comparison is
>, the threshold is
80%, the statistical period is
5 minutes, and the duration is
2 periods, then data on CPU utilization of a CVM will be collected once every 5 minutes, and an alarm will be triggered if the CPU utilization exceeds 80% for three consecutive periods.
You can set a repeated notification policy for each alarm rule, so an alarm notification will be sent repeatedly at specified frequency when an alarm is triggered.
Frequency options: never repeat, every 5 minutes, every 10 minutes, and other frequencies that increase exponentially.
Exponential increase means that when an alarm is triggered for the first time, second time, fourth time, eighth time, ..., or 2 to the power of Nth time, alarm notifications will be sent. In other words, the alarm notification will be sent less and less frequently with longer time interval in between, reducing the disturbance caused by repeated notifications.
The default logic for repeated alarm notifications is as follows:
- A trigger template is used to set triggers for one specific Tencent Cloud product.
- After a trigger template is modified, the corresponding alarm policy that has already been applied will be synced to the latest trigger.
After a trigger template associated with alarm policies is edited, the modification will apply to all associated alarm policies.
After a trigger template associated with alarm policies is deleted, all alarm policies associated with the template will become invalid.
When a trigger template is copied, only its trigger conditions and rules will be copied. If the trigger template is associated with alarm policies, the relationship will not be copied.