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 notification content templateCreate content template
Copy page
Download PDFAlarm notification content template
Create content template
Copy pageDownload PDFCreate content template
TLS sends alarm notifications to designated notification channels based on the content defined in the content template. This topic describes how to create a content template.
Background information
An alarm notification content template is a predefined text template that specifies the content and format of alarm notifications. The content template supports adding variables, functions, and text. When sending alarm notifications, TLS automatically replaces variables in the notification content with the corresponding actual values. For detailed lists of content variables, see Content variable.
TLS provides a default content template (default-template) that can not be modified or deleted. You can create custom content templates based on the default template.
Notice
You can define the complete alarm notification content directly in the content template and leave the notification content in the alarm policy blank. For notifications triggered by alarm triggering, you can also configure a general alarm notification structure in the content template and reference the alarm policy's notification content by using the variable {{NotifyMsg}}.
Steps
- Log in to TLS console.
- Select the region where log service is located from the top navigation bar.
- On the left navigation bar, select Common features > Log alarm > Notification management.
- Under the Alarm template tab, click Create alarm template.
- Configure the content template settings.
- Set the template name.
- Set content templates for each notification channel.
- Email
- ConfigurationDescriptionConfigurationDescriptionFixed content languageThe language for fixed content in alarm notifications. Options include Chinese and English.
- English
- Dear Customer: Your account has an alarm ( Account ID:${AccountID}, User name :${AccountName}).
SubjectEmail subjectContentThe alarm notification content supports plain text format, and you can insert variables or functions. For detailed instructions, see Content variable and Content functions.- Click AI generate content, enter the notification content you want to display as prompted, and click AI generate. TLS Agent will automatically analyze your input, and you can fill in the related configuration with one click after analysis is complete. The recommended result is for reference only; you need to verify based on your actual needs.
- Click Fill with default content to use the built-in notification content. For specific information, see Email.
Notice- The notification content after variable rendering can be up to 8 KB. Content exceeding this limit will be truncated.
- Main content left blank uses the default content.
- AI-generated content is only supported in North China 2 (Beijing), South China 1 (Guangzhou), and East China 2 (Shanghai).
- SMS
- ConfigurationDescriptionConfigurationDescriptionFixed content languageThe language for fixed content in alarm notifications. Options include Chinese and English.
- English
- TLS Alarm: Your account has an alarm ( Account ID:${AccountID}, User name :${AccountName}).
ContentThe alarm notification content supports plain text format, and you can insert variables or functions. For detailed instructions, see Content variable and Content functions.- Click AI generate content, enter the notification content you want to display as prompted, and click AI generate. TLS Agent will automatically analyze your input, and you can fill in the related configuration with one click after analysis is complete. The recommended result is for reference only; you need to verify based on your actual needs.
- Click Fill with default content to use the built-in notification content. For details, see SMS.
Notice- We recommend keeping the notification content after variable rendering within 256 characters. Content that exceeds this limit may be truncated.
- Main content left blank uses the default content.
- AI-generated content is only supported in North China 2 (Beijing), South China 1 (Guangzhou), and East China 2 (Shanghai).
- Phone call
- ConfigurationDescriptionConfigurationDescriptionFixed content languageThe language for fixed content in alarm notifications. Options include Chinese and English.
- English
- TLS Alarm: Your account has an alarm ( Account ID:${AccountID}, User name :${AccountName}). Please log in to TLS console to view details.
ContentThe alarm notification content supports plain text format, and you can insert variables or functions. For detailed instructions, see Content variable and Content functions.- Click AI generate content, enter the notification content you want to display as prompted, and click AI generate. TLS Agentill automatically analyze your input, and you can fill in the related configuration with one click after analysis is complete. The recommended result is for reference only; you need to verify based on your actual needs.
- Click Fill with default content to use the built-in notification content. For details, see Phone call.
Notice- We recommend keeping the notification content after variable rendering within 256 characters. Content that exceeds this limit may be truncated.
- Main content left blank uses the default content.
- AI-generated content is only supported in North China 2 (Beijing), South China 1 (Guangzhou), and East China 2 (Shanghai).
- Lark
- ConfigurationDescriptionConfigurationDescriptionTitleThe subject of the alarm notification.ContentAlarm notification content supports Markdown format. You can insert content variables and functions and so on. For detailed instructions, see Content variable and Content functions.
- Click AI generate content, enter the notification content you want to display as prompted, and click AI generate. TLS Agentill automatically analyze your input, and you can fill in the related configuration with one click after analysis is complete. The recommended result is for reference only; you need to verify based on your actual needs.
- Click Fill with default content to use the built-in notification content. For the supported content syntax in Lark, please refer to Lark Rich Text. For Lark alert template content, refer to Lark, DingTalk, WeCom.
Notice- The notification content after variable rendering can be up to 8 KB. Content exceeding this limit will be truncated.
- Main content left blank uses the default content.
- Due to Lark restrictions, if your notification content contains sensitive information such as plain text phone numbers or email addresses, alarm notifications sent through the Lark channel may fail. For more details, see error 230028.
- AI-generated content is only supported in North China 2 (Beijing), South China 1 (Guangzhou), and East China 2 (Shanghai).
- DingTalk
- ConfigurationDescriptionConfigurationDescriptionContentAlarm notification content supports Markdown format. You can insert content variables and functions and so on. For detailed instructions, see Content variable and Content functions.
- Click AI generate content, enter the notification content you want to display as prompted, and click AI generate. TLS Agent will automatically analyze your input, and you can fill in the related configuration with one click after analysis is complete. The recommended result is for reference only; you need to verify based on your actual needs.
- Click Fill with default content to use the built-in notification content. For specific content, see Lark, DingTalk, WeCom.
Notice- The notification content after variable rendering can be up to 8 KB. Content exceeding this limit will be truncated.
- Main content left blank uses the default content.
- AI-generated content is only supported in North China 2 (Beijing), South China 1 (Guangzhou), and East China 2 (Shanghai).
- WeCom
- ConfigurationDescriptionConfigurationDescriptionContentAlarm notification content supports Markdown format. You can insert content variables and functions and so on. For detailed instructions, see Content variable and Content functions.
- Click AI generate content, enter the notification content you want to display as prompted, and click AI generate. TLS Agent will automatically analyze your input, and you can fill in the related configuration with one click after analysis is complete. The recommended result is for reference only; you need to verify based on your actual needs.
- Click Fill with default content to use the built-in notification content. For specific content, see Lark, DingTalk, WeCom.
Notice- The maximum length for notification content after variable rendering is 4 KB. If it exceeds this limit, the content will be truncated.
- If body text is empty, the default content will be used.
- When you set the reminder method in the notification group to everyone or specified individuals, notifications sent to WeCom will be in plain text format, and Markdown format is not supported.
- AI-generated content is only supported in North China 2 (Beijing), South China 1 (Guangzhou), and East China 2 (Shanghai).
- Custom Webhook
- ConfigurationDescriptionConfigurationDescriptionContentAlarm notification content, usually in JSON format; supports content variables, content functions, and more. For detailed instructions, see Content variable and Content functions.
- Click AI generate content, enter the notification content you want to display as prompted, and click AI generate. TLS Agent will automatically analyze your input, and you can fill in the related configuration with one click after analysis is complete. The recommended result is for reference only; you need to verify based on your actual needs.
- Click Fill with default content to use the built-in notification content. For details, see Custom Webhook.
Notice- The maximum length for notification content after variable rendering is 16 KB. If it exceeds this limit, the content will be truncated.
- Main content left blank uses the default content.
- AI-generated content is only supported in North China 2 (Beijing), South China 1 (Guangzhou), and East China 2 (Shanghai).
- Click Reset.
- The system automatically validates the configured content variables and syntax. If an error message appears, modify the content based on the message.
Default content
TLS provides default notification content; you can set custom notification content based on the default.
Email
Alarm policy：{{Alarm}}<br>
Alarm log project：{{ProjectName}}<br>
Alarm log topic：{{AlarmTopicName}}<br>
Alarm level：{{Severity}}<br>
Triggering time：{{StartTime}}<br>
Triggering condition：{{Condition}}<br>
Notification type：{%if NotifyType==1%}trigger alarm{%else%}Alarm restore{%endif%}<br>
Alarm duration：{{Duration}}<br>
Additional notification：{{NotifyMsg}}<br>
Log query details：[View details]({{QueryUrl|safe}})<br>
Alarm details：[View details(Link expires after 12 hours)]({{SignInUrl|safe}})<br>
SMS
Alarm policy{{Alarm}}， Alarm project：{{ProjectName}}， Alarm topic：{{AlarmTopicName}}， Alarm severity level：{{Severity}}， Notification type：{%if NotifyType==1%}trigger alarm{%else%}Alarm restore{%endif%}，First-alarm time：{{StartTime}}， Triggering condition：{{Condition}}， Current query result：[{%-for x in TriggerParams-%}{{-x-}} {%-endfor-%}]，\nAdditional notification：{{NotifyMsg}}
Phone call
Notification type：{%if NotifyType==1%}Triggering alarm{%else%}Alarm restore{%endif%}
Lark, DingTalk, WeCom
Dear uers, hello!\nYour account (Main account ID{{AccountID}} ）Torch Log Service{%if NotifyType==1%}trigger alarm{%else%}Alarm restore{%endif%}\nAlarm policy：{{Alarm}}\nAlarm topic：{{AlarmTopicName}}\nAlarm level：{{Severity}}\nFirst-alarm time：{{StartTime}}\nTriggering condition：{{Condition}}\nCurrent query result：[{%-for x in TriggerParams-%}{{-x-}} {%-endfor-%}]\nAdditional notification：{{NotifyMsg|escapejs}}\nlog query details: [view details]({{QueryUrl|safe}})\nAlarm details：[view details(The link expires after 12 hours)]({{SignInUrl|safe}})\n\nThanks for your support for Volcanoengine.
Custom Webhook
{
"msg_type": "interactive",
"card": {
"config": {
"wide_screen_mode": true
},
"elements": [
{
"content": "Dear uers, hello!\nYour account (Main account ID{{AccountID}} ）Torch Log Service{%if NotifyType==1%}trigger alarm{%else%}Alarm restore{%endif%}\nAlarm policy：{{Alarm}}\nAlarm topic：{{AlarmTopicName}}\nAlarm level：{{Severity}}\nFirst-alarm time：{{StartTime}}\nTriggering condition：{{Condition}}\nCurrent query result：[{%-for x in TriggerParams-%}{{-x-}} {%-endfor-%}];\nAdditional notification：{{NotifyMsg|escapejs}}\n\nThanks for your support for Volcanoengine.",
"tag": "markdown"
}
],
"header": {
"template": "{%if NotifyType==1%}red{%else%}green{%endif%}",
"title": {
"content": "【Volcanoengine】【log service】{%if NotifyType==1%}Triggering alarm{%else%}Alarm restore{%endif%}",
"tag": "plain_text"
}
}
}
}
Custom content format
TLS supports customizing notification content. For content format details, see the following:
Email
Parameter | Data format |
Parameter | Data format |
Line feed | <br> |
Add link | <a href="https://example.com">link</a> |
Bold | <strong>Bold</strong> |
Italic | <i>This can't be real!</i> |
Lark
Notifications sent via Lark support Markdown syntax. The format of relevant elements is shown in the table below. For more information, see Lark rich text.
Parameter | Data format |
Parameter | Data format |
Line feed | Line 1<br />Line 2 Line 1<br>Line 2 |
Italic | *Italic* |
Bold | **Bold** Or __Bold__ |
Strikethrough | ~~Strikethrough~~ |
Hyperlink | <a href='https://open.feishu.cn'></a> |
@everyone | <at id=all></at> |
@Mention | <at id=user_id></at> |
Colored text style | <font color='green'> This is a green text </font> <font color='red'> This is a red text </font> <font color='grey'> This is a grey text </font> |
Text link | [Open platform](https://open.feishu.cn/) |
Image |  |
Divider | \n ---\n |
Ordered list | 1. Ordered List 1 1. Ordered List 1.1 2. Ordered List 2 |
Unordered list | - Unordered List 1 - Unordered List 1.1 - Unordered List 2 |
Tags | <text_tag color='red'>tag text</text_tag> |
DingTalk
Notifications sent via DingTalk support Markdown syntax. The format of relevant elements is shown in the table below. For more information, see message types for custom bot messages.
Parameter | Data format |
Parameter | Data format |
Title | # heading 1 ## heading 2 ### heading 3 #### heading 4 ##### heading 5 ###### heading 6 |
Quotation | > A man who stands for nothing will fall for anything. |
Bold and italic text | **bold** *italic* |
Link | [this is a link](http://name.com) |
Image |  Recommended maximum value: 20 images. |
Unordered list | - item1 - item2 |
Ordered list | 1. item1 2. item2 |
WeCom
Notifications sent via WeCom support Markdown syntax. The format of relevant elements is shown in the table below. For more information, see WeCom notification content Markdown syntax.
Parameter | Data format |
Parameter | Data format |
Title | # heading 1 ## heading 2 ### heading 3 #### heading 4 ##### heading 5 ###### heading 6 |
Bold | **bold** |
Link | [This is a link](http://work.weixin.qq.com/api/doc) |
Inline code segment | `code` |
Quotation | > Quoted text |
Font color | <font color="info">green</font> <font color="comment">grey</font> <font color="warning">orange</font> |
Last updated: 2026.06.01 15:36:05
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
