Torch Log Service
Torch Log Service
Torch Log Service
Document
Product News
Product Overview
Product Billing
User Guide
TLS Agent
AgentLoop
Resource management
Host group
Data collection
LogCollector collection
Introduction to LogCollector
Installation and upgrade
Collect host logs
Collect container logs
LogCollector plugins
Manage LogCollector
general reference
Data import
Cloud product log collection
TOS log collection
DBW log collection
VPN Log collection
VKE log collection
CLB log collection
CloudTrail log collection
CFW log collection
NTA log collection
ALB log collection
APMPlus log collection
veFaaS log collection
VPC log collection
veImageX log collection
TrafficRoute DNS log collection
DDoS log collection
WAF log collection
DCDN log collection
Multi-cloud security platform log collection
APIG log collection
Machine learning task log collection
CR log collection
Volcano Ark application lab log collection
FileNAS log collection
LLM Application Firewall Service log collection
vePFS log collection
Cloud security center log collection
EFS log collection
Data storage
Query and analysis
Configure log indexes
Query log
Analyze logs
Query and analyze logs using third-party tools
Associate external data source for log query
SQL function
SQL syntax
Visualization
Query and analysis charts
Summaries of query and analysis charts
Create dashboard
Use dashboard
Add dashboard filters and variables
Use other systems to analyze logs
Log application
Log applications for product observability
Log applications for large models observability
Coding Agent log app
ModelProvider log app
No-coding Agent log app
Log applications for basic service monitoring
Data processing
Data transformation
Syntax and functions
Global operation function
expression function
Data processing best practices
general reference
Data write processor
Data consumer processor
Data consumption and shipping
Ship logs to TOS
Ship logs to Kafka
Ship logs to Splunk
Alarm
Alarm policy
Alarm notification content
Alarm notification content template
alarm notification channel
Tracing service
Monitor Log Service
API reference
Project management API
Topic management API
Shard management API
Index management API
Log management API
Host group management API
Collection configuration management API
Data import API
Data processor API
Data transformation API
Data backflow API
SQL analysis API
Alarm management API
Consumer group management API
Kafka protocol consumption API
Tag management API
Trace storage API
Account management API
SDK reference
Go SDK
Java SDK
Python SDK
iOS SDK
C++ SDK
CLI reference
Best practices
Data collection
Query and analysis
permission management
Consumption and delivery
Visualization
Alarm
FAQs
Billing and cost FAQ
Data collection FAQ
Data storage FAQ
Index configuration FAQ
Query and analysis FAQ
Scheduled SQL tasks FAQ
Alarm FAQ
- Documentation
Torch Log ServiceUser GuideAlarmAlarm policyMonitor alarm policy
Copy page
Download PDFAlarm policy
Monitor alarm policy
Copy pageDownload PDFMonitor alarm policy
This topic describes how to monitor alarm policies and stay informed about execution results in time.
Background information
By default, after creating an alarm policy, you can view its execution results in the alarm history statistics chart. However, by default, the system does not automatically send notifications about execution results. For instructions on viewing execution results, see View execution details.
To help you stay updated on the execution status of alarm policies, TLS offers an alarm policy monitoring feature. When you create an alarm for a specified alarm policy, if it fails during execution, the system automatically triggers an alarm and sends a notification to the specified notification group.
Currently, TLS provides alarm policy templates for alarm policy execution failures. This template comes with a preset query and analysis statement, trigger conditions, alarm sending intervals, and other configurations. You only need to add a notification group to complete the alarm policy setup. When the alarm policy encounters the following errors, the system promptly sends notifications to your designated notification group.
Error Code | Description |
Error Code | Description |
QueryError | Analysis statement execution exception. Check your analysis statement and the index configuration for the log topic. |
AlarmConfigNotFound | Alarm policy configuration missing. Check whether the alarm policy and monitored objects are properly configured. |
QuerySyntaxError | The analysis statement for the monitored object contains a syntax error. Please check if the statement is correct. |
QueryResultParseError | Failed to parse the format of the analysis result. |
SendFail | Failed to send notification. |
InternalServerError | Internal server error. |
PartialSent | Successfully sent partial alarms. |
AlarmConditionSyntaxError | Syntax error in alarm conditions. |
AlarmConditionEvaluateError | Expression calculation error in alarm. |
AlarmConditionValueTypeError | Result type error in alarm expression. |
Prerequisites
- An alarm policy has been created. For details, see Create alarm policy.
- A notification group has been created. For details, see Create a notification group.
Steps
- Log in to TLS console.
- Select the region where log service is located from the top navigation bar.
- In the left navigation bar, select Common features > Log alarm > Alarm policy.
- On the Alarm policy page, locate the alarm policy that failed to execute. In its Actions column, select ··· > Create failed execution alarm.
-
- On the Create alarm policy page, select Notification group, keep other parameters as default, and then click Create alarm policy.
Last updated: 2026.03.31 11:32:38
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
