This document describes how to create and delete alarm policies and set the default alarm policy.

Use Cases

You can set threshold alarms for the performance consumption metrics of the Tencent Cloud service resources supported by Cloud Monitor. You can also set event alarms for the service status of Tencent Cloud service instances or the underlying platform infrastructure. This way, when an exception occurs, you will promptly receive notifications, which will allow you to take appropriate measures. An alarm policy consists of five required parameters: name, policy type, alarm trigger condition, alarm object, and alarm channel. You can create alarm policies by following the directions below:

Directions

Creating an alarm policy

1. Log in to the Cloud Monitor console.
2. Choose Alarm Configuration > Alarm Policy to access the alarm policy configuration page.
3. Click Add and configure a new alarm policy, as shown below:
   

   Configuration Type	Configuration Item	Description
   Basic configurations	Policy names	Custom policy names
   	Notes	Notes on custom policies
   	Policy types	Select the desired policy type for monitoring Tencent Cloud services.
   	Projects	This configuration item has two functions: It manages alarm policies. After setting a project, you can quickly locate the alarm policies of a project 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 Projects for Instances to assign projects to the corresponding instances. If you do not have project permissions, see Cloud Access Management (CAM) to obtain permissions.
   	Alarm objects	If you select "all objects", the alarm policy will be associated with all instances under the current account. If you select "some objects", the alarm policy will be associated with the selected instances. If you select "instance group", the alarm policy will be associated with the selected instance group.
   Alarm trigger conditions	Configuring trigger conditions (metric alarms)	An alarm trigger condition is a semantic condition consisting of metric, comparison, threshold, measurement period, and duration. For example, if the metric is CPU utilization, the comparison is `>`, the threshold is `80%`, the measurement period is `5 minutes`, and the duration is `2 periods`, then data on the 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. 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 an alarm is triggered. After 24 hours, the alarm notification will be sent once every day by default.
   	Configuring trigger conditions (event alarms)	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. For more information, see Event Center.
   	Trigger condition templates	Enable "Trigger Condition Template" and select a configured template from the drop-down list. For detailed configurations, see Configuring trigger condition templates. If the created template is not displayed, click **Refresh** on the right.
   Alarm channels	Receiving objects	You can configure the receiving group or recipient as needed. If you do not have the permission to bind the receiving object, refer to Cloud Access Management (CAM) to obtain permissions.
   	Effective periods	You can set custom effective periods for alarm notifications. By default, the effective period is all day (00:00:00 - 23:59:59).
   	Receiving channels	Email and SMS are supported. Before configuring the email/SMS receiving channel, go to the Cloud Access Management console to check whether your email and SMS have been verified. If they have not been verified, you will not be able to receive alarm notifications. For each alarm type, each user has a monthly quota of 1,000 free text messages per month. After this quota is exceeded, you will not be able to receive SMS alarm notifications. You can refer to SMS Channel to purchase a higher SMS quota.
   API callbacks	-	Your system can directly receive Tencent Cloud alarm notifications through the callback API. For more information, see Callback API.

4. After configuring the above information, click Save. The alarm policy has been created successfully.

   Note：

   CVM alarms can be sent normally only after the monitoring Agent has been installed on CVM instances and reports monitoring metric data. On the Cloud Monitor page, you can view CVM instances that do not have Agent installed and download the IP address list.

Deleting an alarm policy

Note：

The Enabled/Instances field in the alarm policy list displays the number of alarm objects associated with the alarm policy. If the value is not 0, the policy cannot be deleted. Only when all alarm objects are disassociated can the policy can be deleted.

Case 1: the alarm policy is not associated with instances.

Click Delete in the alarm policy list.

Case 2: the alarm policy is associated with instances.

1. On the alarm policy list, click the name of the alarm policy you want to delete to go to the alarm policy management page.
2. In the Alarm Object module, click Disassociate All and confirm the disassociation in the pop-up window. If instances are deployed in multiple regions, you need to repeat this step until all instances in all regions have been disassociated.
   
3. After all instances are disassociated from the policy, return to the alarm policy list page and click Delete.

Default alarm policy

Currently, the default alarm policy is only supported for: CVM-basic monitoring, TencentDB for MongoDB, TencentDB for MySQL-CVM monitoring, TencentDB for Redis, TencentDB for CynosDB-MySQL, TencentDB for CynosDB-PostgreSQL, Messaging Service CKafka-Instance, and Elasticsearch.

• When you successfully purchase a Tencent Cloud service that supports the default policy for the first time, Cloud Monitor will automatically create the default alarm policy for you. For more information on the metrics/events supported by the default policy or alarm rules, see the default policy of Tencent Cloud services.
• You can also manually create an alarm policy and set it as the default alarm policy. After the default policy is set, newly purchased instances will be automatically associated with the default policy without requiring manual addition.
  

Note：

Only one default policy is allowed for each policy type in each project.

The default alarm policy cannot be deleted.

The default policy of Tencent Cloud services is as follows: