tencent cloud

All product documents
Cloud Log Service
Viewing Alarm Records
Last updated: 2024-01-20 17:59:35
Viewing Alarm Records
Last updated: 2024-01-20 17:59:35
This document shows how to view alarm records in the CLS console.

Directions

1. Log in to the CLS console.
2. 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 are described as follows.
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.
HappenThreshold Unreached: the period convergence condition is not met; for example, an alarm is triggered only if the trigger condition is met in 5 consecutive monitoring periods.
AlertThreshold Unreached: the alarm interval condition is not met; for example, an alarm will be triggered once every 15 minutes.
TemplateUnmatched
The alarm configuration information doesn't match the notification template. Specific causes include:
TypeUnmatched: the alarm notification type (alarm triggered or alarm cleared) doesn't match the notification template, so no alarm notification is sent.
TimeUnmatched: the alarm notification time period doesn't match the notification template, so no alarm notification is sent.
SendFail: the notification failed to be sent.
Matched
The alarm condition is met, and the alarm notification is sent successfully.
Policy alarm states are described as follows.
Alarm State
Description
Uncleared
The system continuously meets the trigger condition and triggers an alarm.
Cleared
The current monitoring period does not meet the trigger condition.
Invalid
The alarm policy is deleted or modified.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

7x24 Phone Support