Docs

Observability Platform

Notification objects

Callback URLs

When configuring a notification policy, if notification messages need to be received via Webhook, you need to create a callback URL. This topic describes how to create and manage a callback URL.

Background

The egress IP addresses used by different products to send messages via the general callback URL are as follows:

Cloud service	Region	Egress IP address
Cloud Monitor	Chinese mainland	101.126.49.16/28, 101.126.49.32/28, 221.194.189.0/24, 101.126.49.32, 101.126.49.33, 101.126.49.34
Cloud Monitor		Regions outside the Chinese mainland	101.47.0.0/24 , 145.223.191.128/26, 145.223.191.0/25, 145.223.191.192/26
Cloud product event	Chinese mainland	101.126.49.16/28, 101.126.49.32/28, 221.194.189.0/24, 101.126.49.32, 101.126.49.33, 101.126.49.34
Cloud product event		Regions outside the Chinese mainland	101.47.0.0/24 , 145.223.191.128/26, 145.223.191.0/25, 145.223.191.192/26
Volcengine Managed Service for Prometheus	Chinese mainland	101.126.49.32/28、101.126.49.16/28、118.145.64.64/28、118.145.64.80/28、14.103.32.192/28、14.103.32.208/28
Volcengine Managed Service for Prometheus		Regions outside the Chinese mainland	145.223.191.128/26、145.223.191.0/25、145.223.191.192/26
Server-side Monitoring	Chinese mainland	180.184.79.11, 180.184.141.182, 118.145.68.136, 101.47.76.223, 101.47.47.14, 163.7.12.169
Server-side Monitoring		Regions outside the Chinese mainland	101.47.76.223, 101.47.47.14, 163.7.12.169

Limits

Currently, you can create up to 1,000 callback URLs.

Create a callback URL

In the left navigation pane, select "Alert Center -> Notification configuration" to go to the "Notification configuration" page.

On the Notification object tab, select Callback address to enter the callback address management page.

Click Create callback address and configure the relevant parameters as needed.

Parameter	Description
Callback address name	Specify a name for the callback URL. The name serves as a unique identifier for the callback URL. Duplicate names are not allowed.
Channel	Select the channel included in the current callback URL and configure key information such as the callback URL and Secret. tip The Feishu Secret, DingTalk Secret, custom Token, and custom Header must be consistent with the original configuration. Otherwise, the connection will fail. For example, if signature verification is enabled when you configure the Feishu custom bot, you need to enter the Feishu Secret here.
		Lark swarm robot: You need to configure the Feishu callback URL and Feishu Secret. For instructions on how to obtain the values and more details, see Configuring Feishu bots.
		Lark application robot: You need to complete Feishu user authentication and authorization, and select a group that has the "Volcano Engine Observability Alerting Bot" added. For authorization methods and more detailed instructions, see Configuring Feishu application bots. warning The system does not automatically detect which groups have the Feishu application bot added. Make sure that you select a group that has the Feishu application bot added. Otherwise, alert notifications may not be received as expected.
		WeCom: You need to configure the WeCom callback URL. You can also configure the "@user" mention. For instructions on how to obtain the values and more details, see Configuring WeCom bots. tip "@user" is configured using WeCom account IDs. Multiple users can be configured. The "@user" setting in the callback URL is a persistent mention. These users will be @mentioned in every message.
		DingTalk: You need to configure the DingTalk callback URL and DingTalk Secret. You can also configure "@user" and "@phone number" mentions. For instructions on how to obtain the values and more details, see Configuring DingTalk bots. tip "@user" is configured using DingTalk account IDs. Multiple users can be configured. The "@user" and "@phone number" settings in the callback URL are persistent mentions. These users will be @mentioned in every message.
		Slack: You need to configure the Slack callback URL. For instructions on how to obtain the value, see the official documentation.
		General callback address: You need to configure a custom callback URL, custom Token, and custom Header as needed. For the egress IP addresses used to send messages via the general callback URL, see the description in the Background section.

After you configure the parameters, click Connectivity testing in the lower-left corner. Once the connection is verified, click OK in the lower-right corner to finish the configuration.

Managing callback URLs

Click a button in the "Actions" column to the right of the target callback URL to perform the corresponding operation. The currently supported management operations are as follows:

Actions	Description
Edit	Edit the configuration information of an existing callback URL.
Delete	Delete a callback URL that is no longer needed. warning If a callback URL is already associated with notification policies, deleting the callback URL will also disassociate notification policies.

Last updated: 2026.09.07 19:40:06