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 policyAlarm policy testing
Copy page
Download PDFAlarm policy
Alarm policy testing
Copy pageDownload PDFAlarm policy testing
TLS supports testing alarm and previewing alarm notifications when configuring alarm policy. This topic describes key considerations and steps for alarm testing.
Background information
After configuring an alarm policy in TLS, exceptional situation may exist. For example, alarm details fail to meet expectations or alarm notifications fail to send. To simplify troubleshooting in exception scenarios and preview alarm notification results, you can use the alarm testing feature when creating or editing an alarm policy.
The delivery of alarm notifications can be affected by various factors. Besides alarm configuration and callback address accessibility, channel rate limits may also play a role. As a result, you may pass the test but not receive alerts in the production environment. If you experience exceptions, contact your account manager for assistance.
Test alarms
When creating or editing an alarm policy, you can use the alarm testing feature to preview alarm notification results. After sending the alarm test message, you can view the alarm notification in the corresponding channel. For instructions on creating an alarm policy, see Create alarm policy.
The test function is only used to check whether the alarm policy configuration is correct. It does not actually perform the alarm monitoring task. During testing, the system ignores the alarm triggering conditions and sends notifications directly. Some alarm variables in the notification will not take effect, and their values will be empty.
- If the test is successful, the page will display Test successful.
-
- You will also receive an alarm test notification.
- If there are errors in the alarm trigger conditions, custom callback addresses, or other alarm configurations, the alarm test function returns the corresponding error message. You can troubleshoot the configuration based on the message and retry. For common causes and solutions for alarm test failures, see Common causes of test failures.
Common causes of test failures
When creating an alarm policy, you can use alarm testing to preview notifications and verify your policy configuration. This topic lists alarm test error codes, reasons for errors, and solutions.
Error Code | Error message | Reason for error | Solution |
Error Code | Error message | Reason for error | Solution |
AlarmProjectNotExist | No project (%s) exists. | The project used for alarm monitoring was deleted. | Create a new project and log topic, upload logs, and then recreate the alarm policy in the new project |
AlarmParseSQLErr | Failed to parse alarm execution statement %d: %s | The syntax of the execution statement you entered is incorrect. | In the execution statement dialog box, debug the query and analysis statement until you preview the results that meet your requirements. For details about query and analysis statements, refer to Query overviewand Analysis Overview. |
AlarmParseTriggerConditionErr | Failed to parse alarm trigger condition %d: %s | There is a syntax error in the trigger condition expression you entered. | Update the trigger condition expression in the alarm policy based on the error message. For more details, see trigger conditional expression. |
AlarmNotifyGroupNotExist | No notification group (%s) exists. | The notification group you selected has been deleted. | Create a new notification group and bind it to the alarm policy. |
ErrAlarmUserDefineMsgParseErr | Failed to parse user-defined notification content: %s | The notification content you entered contains a grammar error. | Modify the notification content in the alarm policy according to the error prompt. For syntax details about notification content, see Content variable, Login-free access to the alarm details page, overview. |
ErrAlarmWebhookBodyParseErr | Failed to parse the request body of the webhook in %d place in notification group (%s): %s | The syntax of the WebHook request body you entered is not correct. | Modify the WebHook request body according to the error prompt. |
ErrAlarmCallWebhookErr | The webhook address in %d place in notification group (%s) is incorrect. | Failed to call WebHook address. | Check the availability of WebHook addresses in the notification group. |
ErrAlarmContentTemplateParseErr | Content template (%s) failed to parse: %s | The content template you entered contains syntax errors. | Modify the content template according to the error message. For more details, see Create a content template. |
ErrSendSmsMessageOutOfQuota | SMS from user %s exceeds limited quota. | The SMS notification frequency for the specified IAM user exceeds the quota. | |
ErrMobileNotVerified | Phone number of user %s is not verified. | The mobile number configured in the specified IAM user's profile is not verified. | |
ErrSendVmsMessageOutOfQuota | User %s exceeds the phone limit. | The specified IAM user's phone notification frequency exceeds the limit. | |
ErrEmailNotVerified | The email of user %s is not verified. | The email configured in the personal information of the specified IAM user has not been verified. | |
ErrSendSmsFail | User %s failed to send SMS: %s | Failed to send SMS notification. | Check your phone settings based on the error message and try again later. |
ErrSendVmsFail | Failed to send voice notification to user %s: %s | Failed to send voice notification. | Check your phone settings based on the error message and try again later. |
ErrSendEmailFail | Failed to send email to user %s: %s | Failed to send email notification. | Check your email settings according to the error message and try again later. |
ErrWebhookIntegrationNotExist | The alarm webhook integration (%s) does not exist | The WebHook integration configuration you set has been deleted. | Recreate the WebHook integration configuration and bind the new WebHook integration configuration to your notification group. |
ErrCallWebhookIntegration | Failed to call the alarm webhook integration (%s). Error code: %v. Error message: %s | Failed to call the WebHook address; the HTTP status code displays success; but sending alarm notifications to Feishu, DingTalk, and WeCom failed. | Check and update the WebHook integration configuration based on the error message, and then try again later. |
AlarmDefaultErr | The alarm test failed. Try again later | None | Try again later. |
Last updated: 2026.03.31 11:32:38
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
