- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Practical Tutorial
- Ops Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Target Group APIs
- CreateTargetGroup
- DeleteTargetGroups
- DescribeTargetGroups
- DescribeTargetGroupList
- ModifyTargetGroupAttribute
- AssociateTargetGroups
- DisassociateTargetGroups
- RegisterTargetGroupInstances
- DeregisterTargetGroupInstances
- DescribeTargetGroupInstances
- ModifyTargetGroupInstancesWeight
- DescribeTargetGroupInstanceStatus
- GWLB APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Service Level Agreement
- GWLB Policy
- Contact Us
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Practical Tutorial
- Ops Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Target Group APIs
- CreateTargetGroup
- DeleteTargetGroups
- DescribeTargetGroups
- DescribeTargetGroupList
- ModifyTargetGroupAttribute
- AssociateTargetGroups
- DisassociateTargetGroups
- RegisterTargetGroupInstances
- DeregisterTargetGroupInstances
- DescribeTargetGroupInstances
- ModifyTargetGroupInstancesWeight
- DescribeTargetGroupInstanceStatus
- GWLB APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Service Level Agreement
- GWLB Policy
- Contact Us
You can set threshold alarms for the performance consumption metrics supported by Tencent Cloud Observability Platform (TCOP). In this way, when an exception occurs, you will promptly receive notifications to take appropriate measures. An alarm policy consists of five essential components: name, policy type, alarm trigger condition, alarm object, and alarm notification template. You can create an alarm policy by following the directions below.
Basic Concepts
Term | Definition |
Alarm policy | It consists of alarm name, alarm policy type, alarm trigger condition, alarm object, and alarm notification template. |
Alarm policy type | The alarm policy type identifies the policy category and corresponds to specific cloud products. For example, if you select the CVM policy, you can customize metric alarms for CPU utilization, disk utilization, and so on. |
Alarm trigger condition | It is a semantic condition consisting of a metric, a comparison relationship, a threshold, a statistical period, and N consecutive monitoring data points. |
Monitor type | It includes cloud product monitoring, application performance monitoring, frontend performance monitoring, and cloud automated testing. |
Notification template | A notification template can be quickly reused for multiple policies. It is applicable to various alarm notification scenarios. For details, see Creating Alarm Notification Template. |
Directions
1. Log in to the Tencent Cloud Observability Platform console.
2. Click Alarm Management > Alarm Configuration to enter the alarm policy configuration page.
3. Click New Policy to configure an alarm policy. The configuration instructions are as follows:
Configuration Type | Configuration Item | Description |
Basic info | Policy Name | Custom policy name. |
| Remarks | Custom policy remarks. |
| Monitor type | It includes cloud product monitoring, application performance monitoring, frontend performance monitoring, and cloud automated testing. |
| Policy type | Select a policy type for the cloud product you want to monitor. |
| Associated project | The project has the following two functions: Manage alarm policies. After the project is set, you can quickly find alarm policies under the project in the alarm policy list. Manage instances. Select a project based on your needs and then select instances under the project for the alarm object. You can assign cloud products to various projects based on your business type. To create a project, see Project Management. After creating a project, you can assign the resources of each cloud product to projects in the corresponding cloud product console. Some cloud products do not support project assignment, such as TencentDB for MySQL. In this case, you can refer to Specifying Project for Instance to assign instances to the corresponding project. |
Alarm rule configuration | 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. If you select all objects, the alarm policy will be associated with all instances under the current account. |
| Manual configuration (metric alarm) | An alarm trigger condition is a semantic condition consisting of a metric, a comparison relationship, a threshold, a statistical period, and N consecutive 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 relationship is "greater than" (>), the threshold is 80%, the statistical period is 5 minutes, and there are 2 consecutive monitoring data points, then CPU utilization data 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 times. 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. |
| Template selection | Click Template selection 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. |
| Alarm notification configuration | You can select a preset or custom notification template. Each alarm policy can be bound to three notification templates at most. For details, see Notification Template. |
Advanced configuration | Auto scaling | If it is enabled and configured successfully, the auto scaling policy can be triggered when the alarm condition is met, and scale-in and scale-out will be performed. |
4. After configuring the above information, click Finish to successfully create the alarm policy.
Note:
CVM alarms can be sent normally only after CVM instances are installed with the monitoring component Agent and the monitoring metric data is reported. On the cloud product monitoring page, you can view the CVM instances not installed with Agent and download the IP address list.
Yes
No
Was this page helpful?