Term | Definition |
alarm policy | It consists of the policy name, monitoring type, policy type, alarm object, trigger condition, and alarm notification. |
alarm policy type | The alarm policy type is used to identify the policy category, and types correspond to cloud products. For example, if you select a Cloud Virtual Machine (CVM) policy, you can customize an alarm for metrics such as CPU utilization and disk utilization. |
alarm trigger condition | It is a semantic condition consisting of a metric, a comparison relationship, a threshold, a statistical granularity, and N consecutive monitoring data points. |
monitoring type | It includes Cloud Product Monitoring, CLS, APM, RUM, Cloud Probe Monitor, and Terminal Performance Monitoring. |
notification template | A template can be reused by multiple policies with one click, and is suitable for receiving alarm notifications in various scenarios. For details, see Creating an Alarm Notification Template. |
Configuration Type | Configuration Item | Description |
Basic Information | Policy Name | Custom policy name. |
| Remarks | Custom policy remarks. |
| Policy 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 Rule Configuration | Monitoring Type | Supports Cloud Product Monitoring, CLS, APM, RUM, Cloud Probe Monitor, 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. |
| 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 object: 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 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 object: You can first define the monitoring scope by filtering region, business system, call role, and so on, and then specify the object dimension for alarm evaluation. The system performs alarm detection for each object of the selected dimension within the filtered scope. Multi-dimension combinations can meet the refined monitoring requirements of complex scenarios. |
| Trigger Condition | An alarm trigger condition is a semantic condition consisting of a metric, a comparison relationship, a threshold, a statistical granularity, and N consecutive 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 five 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. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback