- Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Resource Management
- Log Collection
- Log Search
- Log Analysis
- Log Shipping
- Log Consumption
- Permission Management
- CAM Access Authorization
- Resource List
- Action List
- Granting a Sub-account Permissions for CLS
- Granting a Sub-account Full Permissions for CLS Resources
- Granting a Sub-account Read-only Permission for CLS Resources
- Granting a Sub-account Permissions for Embedded CLS Console
- Granting a Sub-account Full Permissions for a CLS Log Topic
- Granting a Sub-account Read-only Permission for a CLS Log Topic
- Granting a Sub-account Permissions to Collect Logs for a CLS Log Topic
- Monitoring Alarm
- Function Processing
- Developer Guide
- API Documentation
- Glossary
- FAQs
- Service Level Agreement
- Appendix
- Notices
- Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Resource Management
- Log Collection
- Log Search
- Log Analysis
- Log Shipping
- Log Consumption
- Permission Management
- CAM Access Authorization
- Resource List
- Action List
- Granting a Sub-account Permissions for CLS
- Granting a Sub-account Full Permissions for CLS Resources
- Granting a Sub-account Read-only Permission for CLS Resources
- Granting a Sub-account Permissions for Embedded CLS Console
- Granting a Sub-account Full Permissions for a CLS Log Topic
- Granting a Sub-account Read-only Permission for a CLS Log Topic
- Granting a Sub-account Permissions to Collect Logs for a CLS Log Topic
- Monitoring Alarm
- Function Processing
- Developer Guide
- API Documentation
- Glossary
- FAQs
- Service Level Agreement
- Appendix
- Notices
This document shows how to view alarm records in the CLS console.
Directions
- Log in to the CLS console.
- On the left sidebar, click Monitoring Alarm > Alarm Records to enter the alarm records page.
Notes
CLS allows you to view the alarm records in the last 30 days.
Alarm statistics
Alarm Statistics displays important information on alarms in the current region, such as alarm policy statistics and monitoring task execution. The metrics are as detailed below:
| Metric | Description |
|---|---|
| Total Alarm Policy Executions | Number of alarm policies executed over the statistical time range |
| Alarm Policy Executions | Number of times the query and analysis statement in the alarm policy is executed over the statistical time range |
| Failed Alarm Policy Executions | Number of alarm policy execution failures over the statistical time range. Execution failures include AlarmConfigNotFound, QuerySyntaxError, QueryError, QueryResultParseError, ConditionSyntaxError, ConditionEvaluateError, and ConditionValueTypeError. For more information, please see Execution Result Status Codes |
| Times of Trigger Conditions Met | Number of times the query and analysis statement in the alarm policy is executed successfully and the result returned meets the trigger condition over the statistical time range |
| Notifications Triggered by the Alarm Policy | Number of times notifications are triggered by the execution of the alarm policy over the statistical time range |
| Top 10 Alarm Policies by Number of Notifications | Top 10 alarm policies in terms of the number of times notifications are triggered over the statistical time range |
Historical records
Once an alarm policy takes effect, it will periodically perform monitoring tasks, and the details of executions of each monitoring task will be recorded in Historical Records, including the result of each execution. By viewing the records of alarm policy execution, you can easily trace back historical alarming tasks.
Note：
CLS allows you to view the records in the last 30 days.
Policy execution results:
| Execution Result | Description |
|---|---|
| AlarmConfigNotFound | The alarm policy configuration is missing. Please check whether the alarm policy and monitoring object have been configured correctly. |
| QuerySyntaxError | The analysis statement of the monitoring object has a syntax error. Please check whether the statement is correct. For more information on the syntax, please see Overview. |
| QueryError | The analysis statement is not executed properly. Please check the analysis statement and the index configuration of the log topic. |
| QueryResultParseError | Failed to parse the analysis result format. |
| ConditionSyntaxError | The trigger condition expression has a syntax error. Please check the syntax format of the expression. |
| ConditionEvaluateError | An error occurred while computing the trigger condition. Please check whether the imported variable exists in the analysis result. |
| ConditionValueTypeError | The evaluation result of the trigger condition is not a Boolean value. Please check whether the trigger condition expression is correct. |
| EvalTimesLimited | The trigger condition hasn't been met even after it has been computed more than 1,000 times. |
| QueryResultUnmatch | The analysis result for the current monitoring period doesn't meet the alarm trigger condition. |
| UnreachedThreshold | The alarm trigger condition is met, but the alarm convergence threshold has not been reached, so no alarm notification is sent. |
| TemplateUnmatched | The alarm configuration information doesn't match the notification template. Specific causes include: |
| Matched | The alarm condition is met, and the alarm notification is sent successfully. |
Notification status:
| Notifications Sent | Description |
|---|---|
| No notifications sent | No notification is triggered because the query and analysis failed, the trigger condition is not met, or the alarm is converged when the policy executes a task. |
| All sent successfully | An alarm notification is triggered and is sent successfully to all recipients in the notification template. |
| Some sent successfully | An alarm notification is triggered and is sent successfully to some recipients in the notification template (possibly because the notification receipt channel has changed or hasn't been verified). |
Yes
No
Was this page helpful?