Term | Definition |
Alarm policy | It consists of alarm name, alarm policy type, alarm trigger condition, alarm object, and alarm notification template |
Alarm policy type | Alarm policy type identifies policy category and corresponds to specific Tencent Cloud products. For example, if you choose the CVM policy, you can customize metric alarms for CPU utilization, disk utilization, and more |
Alarm trigger condition | An alarm trigger condition is a semantic condition consisting of metric, comparison, threshold, statistical period, and N consecutive monitoring data points |
Monitor type | Types include Tencent Cloud service monitoring, application performance monitoring, frontend performance monitoring, and cloud automated testing |
Notification template | A notification template can be quickly reused for multiple policies, making it suitable for alarm receipt in various use cases. For more information, see Creating Alarm Notification Template |
Configuration Type | Configuration Item | Description |
Basic info | Policy name | Custom policy name |
| Remarks | Custom policy remarks |
| Monitor type | Types include Tencent Cloud service monitoring, application performance monitoring, frontend performance monitoring, and cloud automated testing |
| Policy type | Select the desired policy type for monitoring Tencent Cloud services. |
| Projects | This configuration item has two functions: Manage alarm policies. Alarm policies of a project can be quickly located in the alarm policy list. It manages instances. Choose a project based on your needs. Then, in "Alarm Object", you can quickly select instances under the project. You can assign Tencent Cloud services to each project based on your business types. If you want to create a project, see Project Management. After creating a project, you can use the console of each Tencent Cloud service to assign projects to resources. Some Tencent Cloud services such as TencentDB for MySQL do not support project assignment. In that case, you can refer to Specifying Project for Instance to assign projects to the corresponding instances. If you do not have project permissions, see Cloud Access Management (CAM) to get permissions. |
Configure alarm rule | Alarm object | If you select "instance ID", the alarm policy will be associated with the selected instance. If you select "instance group", the alarm policy will be associated with the selected instance group. All Objects: associate the policy with all instances under the current account (permission required) |
| Trigger condition(choosing Manual Configuration) | An alarm trigger condition is a semantic condition consisting of metric, comparison, threshold, measurement period, and N monitoring data points. You can set an alarm threshold according to the trend of metric change in the chart. For example, if the metric is CPU utilization, the comparison is `>`, the threshold is `80%`, the measurement period is `5 minutes`, and the consecutive monitoring data points is `2 data points`, then data on the 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 two consecutive periods. Alarm frequency: you can set a repeated notification policy for each alarm rule. This way, an alarm notification will be sent repeatedly at a specified frequency when an alarm is triggered. Frequency options: do not repeat, once every 5 minutes, once every 10 minutes, at an exponentially increasing interval, and other frequency options. An exponentially increasing interval means that a notification is sent when an alarm is triggered the first time, second time, fourth time, eighth time, and so on. In other words, the alarm notification will be sent less and less frequently as time goes on to reduce the disturbance caused by repeated notifications. Default logic for repeated alarm notifications: the alarm notification will be sent to you at the configured frequency within 24 hours after the alarm is triggered. After 24 hours, the alarm notification will be sent once a day by default. |
| Configure manually (event alarm) | You can create event alarms so that when the Tencent Cloud service resources or the underlying infrastructure services encounter any errors, you will promptly receive notifications and can then take measures accordingly. |
| Select template | Click Select template and select a configured template from the drop-down list. For detailed configurations, see Configuring Trigger Condition Template. If a newly created template is not displayed, click Refresh on the right. |
Configure alarm notification | Alarm notification | You can select a preset or custom notification template. Each alarm policy can be bound to three notification templates at most. For more information, see Notification Template. |
Advanced configuration | Auto scaling | After this option is enabled and configured successfully, an auto scaling policy will be triggered for scaling when the alarm condition is met. |
Was this page helpful?