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 GuideAlarmCreate Webhook integration configuration
Copy page
Download PDFAlarm
Create Webhook integration configuration
Copy pageDownload PDFCreate Webhook integration configuration
The Webhook integration configuration manages DingTalk, Lark, WeCom, and custom Webhook alarm notification channels. This topic explains how to create a Webhook integration configuration.
Background information
TLS supports managing Webhook addresses through Webhook integration, enabling alarm notifications to be sent to Lark groups, DingTalk groups, WeCom groups, or other custom Webhook addresses such as self-built systems or third-party alarm systems. When you manage Webhook addresses in this way, the alarm system checks the response of each request to determine whether the notification was sent successfully. Additionally, Webhook integration provides centralized management of all your Webhook addresses. You only need to link the relevant Webhook integration configuration in the alarm group; you do not need to repeatedly configure Webhook addresses.
Webhook security configuration
TLS alarm supports the following security configurations.
- Lark and DingTalk channels
- Custom keywords
- If you configure custom keywords in Lark or DingTalk bots, you need to include at least one of these keywords in the alert notification content from TLS. When using this method, it is recommended to set one of the keywords as alert on the DingTalk or Lark side.
- Signature verification
- If you configure a signing key in Lark or DingTalk bots, you must enter the signing key in the Webhook integration configuration on the TLS side.
- Other custom Webhook addresses
- Use HTTP request headers for permission verification by adding "Authorization": "Bearer ${token}" in the request header. You need to replace ${token} with your custom Token.
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.
- On the notification management page, click the webhook integration tab, and then click Create webhook integration.
- Configure settings in the Create Webhook integration configuration dialog box.
- Set the name for the Webhook integration configuration.
- Select a notification channel type.
- Supported channels: Lark, DingTalk, WeCom, and custom Webhook.
- Complete the configuration based on the notification channel type you selected.
- Lark
- ConfigurationDescriptionConfigurationDescriptionRequest URLWebhook address. You need to add a custom bot in Lark first, and then enter the bot's Webhook address here. For detailed instructions, see the Custom Bot User Guide.Encryption keyWebhook encryption key. Optional. When the security settings for the Lark bot are set to signature verification, enter the bot's signature key here. For detailed instructions, see the Custom Bot User Guide.
- DingTalk
- ConfigurationDescriptionConfigurationDescriptionRequest URLWebhook address. You need to add a custom bot in DingTalk first, and then enter the DingTalk bot's webhook address here. For more details, see Create and install enterprise internal application bot.Encryption keyWebhook encryption key. When you set a signature value in the DingTalk bot, enter the DingTalk bot's signature value here. For detailed instructions, see Developing bots.
- WeCom
- ConfigurationDescriptionConfigurationDescriptionRequest URLWebhook address. Add a custom bot in WeCom first, and then enter the WeCom bot's Webhook URL here. For detailed instructions, see Group bot configuration instructions.
- Custom Webhook
- ConfigurationDescriptionConfigurationDescriptionRequest methodMethods for requesting this Webhook URL. Supports POST and PUT.Request URLWebhook address.
- For self-built systems, you need to implement a callback API on your server for TLS backend calls and provide the request URL.
- For third-party alert systems, please refer to their official documentation for custom callback URLs and request body structures.
Request headerRequest headers for the Webhook URL.TLS provides a default request header "content-type": "application/json". You can also click Add a row to add request headers. TLS includes this information in the request headers of each alert notification.
- Click Create.
Related operations
After creating the Webhook integration configuration, you can also perform the following actions on the Webhook management page.
Actions | Description |
Actions | Description |
View Webhook integration settings | Locate the target Webhook integration in the actions column, and click the integration name to view configuration details. |
Edit Webhook integration settings | Locate the target Webhook integration in the actions column, and click Edit to edit the configuration. |
Copy Webhook integration configuration | Locate the target Webhook integration configuration. In the actions column, click Copy to duplicate a Webhook integration configuration. |
Delete Webhook integration configuration | Locate the target Webhook integration configuration. In the actions column, open the dropdown menu and click Delete to remove this Webhook integration configuration. |
Last updated: 2026.04.14 14:54:24
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
