You can set an alarm rule for a specific Tencent Cloud service through a trigger condition 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. 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 condition 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 the data on CPU utilization of a CVM instance 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: do not repeat, once every 5 minutes, once every 10 minutes, and other exponentially increased frequencies.
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, an alarm notification will be sent to you. In other words, the alarm notification will be sent less and less frequently with longer time intervals in between, reducing the disturbance caused by repeated alarm notifications.
The default logic for repeated alarm notifications is as follows:
- A trigger condition template is used to set triggers for one specific Tencent Cloud service.
- After a trigger condition template is modified, the corresponding alarm policy that has already been applied will be synced to the latest trigger.
After a trigger condition template associated with alarm policies is edited, the modification applies to all associated alarm policies.
After a trigger condition template associated with alarm policies is deleted, all alarm policies associated with the template become invalid.
When a trigger condition template is copied, only the triggers and rules of the template are copied. If the copied template is associated with an alarm policy, the association relationship is not copied.