Docs

Torch Log Service

Alarm FAQ

How to set up Feishu, DingTalk, and WeCom alarm notifications

The log service supports sending alarm notifications in the form of Feishu messages, that is, setting the alarm notifications of the Feishu group robot channel through the custom robot function of the Feishu group. After the alarm is successfully set up and triggered, the logging service sends an alert notification message to the specified Feishu group via the bot.

Configure Feishu bot notifications

Add a custom bot to your Feishu group chat.

Create a custom bot in the Feishu group that needs to receive log service alert notifications. Please refer to the official Feishu documentation for the creation method.

Get the Webhook address of the swarm robot.

Please refer to the official Feishu documentation .

Create an alert group in the Log Services console and fill in the alert group name , notification type , and notification channel .

Wherein, the receiving channel is specified as a custom interface callback , and the custom interface callback configuration is specified. Please refer to other parameter configuration methods Create notification group.

Configuration	Description
request method	The request method of the callback interface. This should be set to the POST method.
request address	The request address of the callback interface must be filled in the webhook address obtained in step 2, such as https://open.feishu.cn/open-apis/bot/v2/hook/xxxxxxxxxxxxxxxxx .
request header	Request header field configuration. It is recommended to keep the "content-type": "application/json" field populated by the logging service by default. You can also refer to the official Feishu documentation to append the request header information.
content template	The specific content of the alarm notification, the format must comply with the callback interface requirements of the Feishu open API . The log service sends alert notifications as defined in the send content content template. Please refer to the configuration method of the content template Create content template. You can also use the default template provided by the logging service directly, which is for Feishu swarm robots.

To observe the visit of a website as an example, configure the following content template:

{
"msg_type": "interactive",
"card": {
"config": {
"wide_screen_mode": true
},
"elements": [
{
"content": "Dear users, hello！\nYour account（main accountID：{{AccountID}} ）log service {%if NotifyType==1%}triggers an alarm{%else%}Alarm recovery{%endif%}\nAlarm policy：{{Alarm}}\nAlarm log topic：{{AlarmTopicName}}\nTriggering time：{{StartTime}}\nTriggering condition：{{Condition}}\nCurrent query result：[{%-for x in TriggerParams-%}{{-x-}} {%-endfor-%}];\nNotification content：{{NotifyMsg|escapejs}}\n\nThanks for your support to Volcanoengine",
"tag": "markdown"
}
],
"header": {
"template": "{%if NotifyType==1%}red{%else%}green{%endif%}",
"title": {
"content": "【Volcanoengine】【Torch log service】{%if NotifyType==1%}Triggeing alarm{%else%}Alarm recovery{%endif%}",
"tag": "plain_text"
}
}
}
}

Check the alarm notification.

Configure WeCom Notifications

Add custom bots to WeCom group chats.

Create a custom bot in the WeCom group that needs to receive log service alert notifications. Please refer to the official WeCom documentation for the creation method.

Get the webhook address of the swarm robot.

Please refer to the official WeCom documentation .

Create an alert group in the Log Services console and fill in the alert group name , notification type, and notification channel .

Among them, in the notification channel, the receiving channel is specified as a custom interface callback, and the custom interface callback configuration is specified. Please refer to other parameter configuration methods Create notification group.

configuration	description
request method	The request method of the callback interface. This should be set to the POST method.
request address	The request address of the callback interface must be filled in the webhook address obtained in step 2, such as https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=693a91f6-7xxx-4bc4-97a0-0ec2sifa5aaa .
request header	Request header field configuration. It is recommended to keep the "content-type": "application/json" field populated by the logging service by default. You can also refer to the official WeCom documentation to append the request header information.
request body	The specific content of the alarm notification, the format must comply with the callback interface requirements of WeCom . The log service sends alert notifications as defined in the send content content template. Please refer to the configuration method of the content template Create content template..

To observe the visit of a website as an example, configure the following content template:

{
"msgtype": "text",
"text": {
"content": " [Volcanoengine][Torch log service]{%if NotifyType==1%}Triggering alarm{%else%}Alarm recovery{%endif%} \nDear users, hello！\nYour account（main accountID：{{AccountID}}，username：{{UserName}}）log service triggers alarm\nTriggering policy：{{Alarm}}\nAlarm log topic：{{AlarmTopicName}}\nTriggering time：{{StartTime}}\nTriggering condition：{{Condition}}\nCurrent query result：[{%-for x in TriggerParams-%}{{-x-}}, {%-endfor-%}];\nNotification content：{{NotifyMsg}}\n\n\nThanks for your support to Volcanoengine"
}
}

Check the alarm notification.

The alarm notification effect of the WeCom swarm robot is shown in the following figure:

Configure DingTalk swarm bot notifications

Add custom bots to your DingTalk group chat.

Create a custom bot in the DingTalk group that needs to receive log service alert notifications. Please refer to the official DingTalk documentation .

Get the webhook address of the swarm robot.

Please refer to the official DingTalk documentation .

Create an alert group in the Log Services console and fill in the alarm group name , notification type , and notification channel .

Among them, in the notification channel, the receiving channel is specified as a custom interface callback, and the custom interface callback configuration is specified. Please refer to other parameter configuration methods Create notification group.

configuration	description
request method	The request method of the callback interface. This should be set to the POST method.
request address	The request address of the callback interface must be filled in the webhook address obtained in step 2, such as https://oapi.dingtalk.com/robot/send?access_token=XXXXXX .
request header	Request header field configuration. It is recommended to keep the "content-type": "application/json" field populated by the logging service by default. You can also refer to the DingTalk open API official documentation to append request header information.
request body	The specific content of the alarm notification, the format must meet the callback interface requirements of the DingTalk open API . The log service sends alert notifications as defined in the send content content template. Please refer to the configuration method of the content template Create content template.

To observe the visit of a website as an example, configure the following content template:

{
"msgtype": "text",
"text": {
"content": " [Volcanoengine][Torch log service]{%if NotifyType==1%}Triggering alarm{%else%}Alarm recovery{%endif%} \nDear users, hello！ \nYour account（main accountID：{{AccountID}}）log service triggers alarm \nAlarm policy：{{Alarm}} \nAlarm log topic：{{AlarmTopicName}} \nTriggering time：{{StartTime}} \nTriggering condition：{{Condition}} \nCurrent query result：[{%-for x in TriggerParams-%}{{-x-}}, {%-endfor-%}] \nNotification content：{{NotifyMsg}} \nThanks for your support to Volcanoengine"
},
"at": {
"isAtAll": true
}
}

Check the alarm notification.

Last updated: 2026.06.25 17:33:46