Integrate a custom webhook
When you use a custom webhook for DataWorks monitoring and alerting, DataWorks pushes alert messages to your webhook service over the public network by default. You can select a connection method based on the deployment environment of the webhook service. To use the public network method, add the DataWorks public egress IP addresses to the allowlist of the webhook service. To use the internal network method, specify a resource group that can connect to the webhook service in the tenant alert policy, and the resource group sends the alert messages. This ensures that alert messages are delivered.
Usage notes
-
Network limits: Alert messages are pushed over the public network by default. If your webhook service is deployed in an internal network, you can specify a resource group that can connect to the webhook service in the tenant alert policy, and the resource group sends the alert messages. For more information about the two connection methods, see public network configuration and internal network configuration.
-
Edition limits: Custom webhooks are supported only in DataWorks Enterprise Edition.
Public network configuration
By default, DataWorks pushes alert messages to your webhook service over the public network, and no additional network configuration is required.
Skip this step if your webhook service does not use allowlist-based access control.
If your webhook service uses an allowlist for access control, add the following public IP addresses of DataWorks to that allowlist.
|
Region name |
Region ID |
IP address |
|
China (Beijing) |
cn-beijing |
47.93.5.9,47.93.60.157,47.94.111.106,59.110.166.34,60.205.184.153,60.205.227.157,60.205.223.44,123.56.217.46,123.57.155.168,123.57.243.71 |
|
China (Zhangjiakou) |
cn-zhangjiakou |
39.100.0.109,39.100.9.117,39.100.9.121 |
|
China (Hangzhou) |
cn-hangzhou |
47.96.30.97,47.97.175.135,116.62.247.242,120.27.233.168,121.40.70.19,121.199.31.66,121.199.41.143,121.199.61.16 |
|
China (Shanghai) |
cn-shanghai |
47.100.10.242,47.101.166.155,47.101.179.29,47.101.196.116,101.132.179.94,106.14.1.102,106.15.197.122,106.15.202.114 |
|
China (Shenzhen) |
cn-shenzhen |
47.107.81.9,47.112.11.104,47.112.21.108,47.112.22.239,47.112.23.85 |
|
Malaysia (Kuala Lumpur) |
ap-southeast-3 |
47.254.198.127,47.254.200.185 |
|
Japan (Tokyo) |
ap-northeast-1 |
47.74.22.81,47.74.23.43 |
|
South Korea (Seoul) |
ap-northeast-2 |
47.80.13.207,47.80.10.92 |
|
China (Chengdu) |
cn-chengdu |
47.108.64.120,47.108.119.242 |
|
Singapore |
ap-southeast-1 |
47.74.209.97,47.74.229.187,47.74.243.124 |
|
Indonesia (Jakarta) |
ap-southeast-5 |
149.129.253.151,149.129.253.185 |
|
China (Hong Kong) |
cn-hongkong |
47.52.128.224,47.244.33.205 |
|
Germany (Frankfurt) |
eu-central-1 |
47.91.89.154,47.254.153.91 |
|
US (Virginia) |
us-east-1 |
47.89.191.99,47.90.253.133 |
|
US (Silicon Valley) |
us-west-1 |
47.88.4.25,47.88.6.226 |
|
UK (London) |
eu-west-1 |
8.208.12.7,8.208.15.6 |
|
China East 2 Finance |
cn-shanghai-finance-1 |
139.224.120.181,139.224.122.217,139.224.144.132,139.224.145.23,139.224.149.100 |
|
China South 1 Finance |
cn-shenzhen-finance-1 |
112.74.242.199,112.74.244.59,112.74.246.74,112.74.246.212 |
|
China North 2 Finance |
cn-beijing-finance-1 |
8.141.252.42,8.141.252.231 |
|
China North 2 Ali Gov 1 |
cn-north-2-gov-1 |
39.107.177.30,39.107.177.140 |
|
SAU (Riyadh - Partner Region) |
me-central-1 |
8.213.30.84,8.213.30.232 |
Internal network configuration
If your webhook service is deployed in an internal network, you can specify a resource group that can connect to the webhook service for the custom webhook in the tenant alert policy. The resource group sends alert messages. This way, alert messages do not leave the internal network and are transmitted in a more secure manner.
-
Log on to the DataWorks console and go to the Operation Center. In the left-side navigation pane, click .
-
Click Tenant Alert Policy Settings.
-
Select a resource group that can connect to your webhook service for Custom Webhook Resource Group (only Serverless resource groups are supported) to complete the configuration. For more information about tenant alert policies, see Rule management. For more information about how to configure network connectivity for a resource group, see Configure network connectivity.
If no resource group is selected, custom webhooks in the tenant send alert messages over the public network by default. After the configuration takes effect, a message appears at the top of the Alert information page, indicating that resource group-based sending is enabled for custom webhooks in the current tenant. You can click Modify Configuration in the message to change the settings.
Reference
For the message format of custom webhooks used for intelligent monitoring, see Custom webhook message format for intelligent monitoring.