tencent cloud

Configuring Alarm Policy

PDF
Focus Mode
Font Size
Last updated: 2026-03-31 10:54:05

Scenarios

You can customize alarm policies according to business and system features for different monitoring scenarios. An alarm policy consists of the following six essential parts: policy name, monitoring type, policy type, alarm object, trigger condition, and alarm notification.
This document introduces how to create an alarm policy.

Directions

1. Log in to the Tencent Cloud Observability Platform console.
2. Choose Alarm Management > Alarm Configuration and click Create Policy on the Alarm Policy page to configure an alarm policy. The following table describes the configuration.
Configuration Type
Configuration Item
Description
Basic Info
Policy Name
Custom policy name.
Remarks
Custom policy remarks.
Alarm rule configuration
Monitoring Type
It supports cloud product monitoring, application performance monitoring, frontend performance monitoring, cloud automated testing, and terminal performance monitoring.
Policy type
Select a policy type for the cloud product you want to monitor.
Policy Project
After you select a project to which the policy belongs, the policy permissions remain consistent with the project permissions. To create a project, see Project Management. Meanwhile, this configuration item allows you to manage policies based on projects.
Associated Tag
Select tags for the policy to facilitate policy management by tag. You can associate multiple tags with a single policy. To create a tag, see Tag Management.
Alarm object
The dimensions for alarm objects vary with cloud product policies. Some cloud product policies only support filtering alarm objects by a single dimension, while others support filtering alarm objects by multiple fields, which enables more precise matching and triggering of alarm rules.
Single alarm objects: You can filter alarm objects by instance ID, instance group, or tag, or directly select all instance objects as alarm objects. The tag feature helps you quickly filter Tencent Cloud resources bound with tags. When instances under a tag scale out or in, the alarm policies are updated simultaneously, reducing the secondary modification cost.
Multi-dimensional alarm objects: You can filter alarm objects by multiple fields such as Region, Cluster, and Node. You can also combine multiple filter fields, which helps you define more complex alarm conditions.
Trigger Condition
An alarm trigger condition is a semantic condition composed of metrics, comparison relationship, thresholds, statistical granularity, and continuous N monitoring data points.
You can customize the trigger conditions of metric alarms and event alarms, configure alarm metrics, statistical granularity, alarm thresholds, alarm levels, and alarm frequencies based on business needs, or directly use trigger condition templates and preset trigger conditions. For details, see Configuring an Alarm Trigger Condition.
Alarm notification configuration
Alarm Notification Template
You can select a preset system notification template or customize a notification template. Each alarm policy can be bound to three notification templates at most. For details, see Alarm Notification.
Advanced configuration
Auto scaling
Some cloud products support auto scaling. After authorization and successful configuration, the auto scaling policy can be triggered when the alarm condition is met.
3. After configuring the above information, click Complete to create the policy.
Note:
After the alarm policy is created, the policy item and tag information cannot be changed. Users can click and copy the alarm policy and edit the policy item and tag information of the copied policy.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback