This document describes how to create and delete alarm policies and set the default alarm policy.
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:
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:
|
|
Alarm objects |
|
|
Alarm trigger conditions | Configuring trigger conditions (metric alarms) |
|
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.
|
|
API callbacks | - | Your system can directly receive Tencent Cloud alarm notifications through the callback API. For more information, see Callback API. |
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.
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.
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.
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:
Tencent Cloud Service | Alarm Type | Metric/Event Name | Alarm Rules |
---|---|---|---|
CVM | Metric alarms | CPU utilization | The measurement period is 1 minute; the threshold is >95%; the duration is 5 periods |
Memory utilization | The measurement period is 1 minute; the threshold is >95%; the duration is 5 periods | ||
Disk utilization | The measurement period is 1 minute; the threshold is >95%; the duration is 5 periods | ||
Public bandwidth utilization | The measurement period is 1 minute; the threshold is >95%; the duration is 5 periods | ||
Event alarm | Disk read-only | - | |
TencentDB for MySQL-CVM monitoring |
Metric alarms | Disk utilization | The measurement period is 1 minute; the threshold is >80%; the duration is 5 periods |
CPU utilization | The measurement period is 1 minute; the threshold is >80%; the duration is 5 periods | ||
Event alarm | Memory OOM | - | TencentDB for MongoDB |
Metric alarms | Disk usage | The measurement period is 1 minute; the threshold is >80%; the duration is 5 periods |
Connection usage | The measurement period is 1 minute; the threshold is >80%; the duration is 5 periods | ||
TencentDB for Redis-CKV version/community version |
Metric alarm | Capacity usage | The measurement period is 1 minute; the threshold is >80%; the duration is 5 periods |
TencentDB for CynosDB-MySQL |
Event alarms | Memory OOM | - |
Instance read-only (disk capacity limit exceeded) | TencentDB for CynosDB-PostgreSQL |
Event alarms | Insufficient memory | - |
Memory OOM | |||
Message Queue CKafka-Instance |
Metric alarm | Disk usage percentage | The measurement period is 1 minute; the threshold is >85%; the duration is 5 periods |
Elasticsearch service | Metric alarms | Avg disk usage | The measurement period is 1 minute; the threshold is >80%; the duration is 5 periods |
Avg CPU usage | The measurement period is 1 minute; the threshold is >90%; the duration is 5 periods | ||
Avg JVM memory usage | The measurement period is 1 minute; the threshold is >85%; the duration is 5 periods | ||
Cluster health | The measurement period is 1 minute; the threshold is >=1; the duration is 5 periods |
Was this page helpful?