Webhooks enable you to:
Go to the Webhooks integration tile and enter the URL and name of the webhook you want to use.
To use your webhook, add @webhook-*name_of_the_webhook* in the text of the metric alert you want to trigger the webhook. It triggers a POST request to the URL you set with the following content in JSON format. The timeout for any individual request is 15 seconds.
You can also specify your own payload in order to add your own custom fields to the request. Check the Use Custom Payload checkbox and specify your own custom payload, using the following variables. If you want your payload to be URL-encoded, check the Encode as form payload and specify your payload in JSON format.
| Variable | Meaning |
|---|---|
| $AGGREG_KEY | ID to aggregate events belonging together (e.g.: 9bd4ac313a4d1e8fae2482df7b77628). |
| $ALERT_CYCLE_KEY | ID to link events from the time an alert triggers until it resolves. |
| $ALERT_ID | ID of alert (e.g.: 1234). |
| $ALERT_METRIC | Name of the metric if it’s an alert (e.g.: system.load.1). |
| $ALERT_QUERY | Query of the monitor that triggered the webhook. |
| $ALERT_SCOPE | Comma-separated list of tags triggering the alert (e.g.: availability-zone:us-east-1a, role:computing-node). |
| $ALERT_STATUS | Summary of the alert status (e.g.: system.load.1 over host:my-host was > 0 at least once during the last 1m). |
| $ALERT_TITLE | Title of the alert. |
| $ALERT_TRANSITION | Type of alert notification (values: Recovered, Triggered/Re-Triggered, No Data/Re-No Data, Warn/Re-Warn, Null, Renotify). |
| $ALERT_TYPE | Type of the alert. |
| $DATE | Date (epoch) where the event happened (e.g.: 1406662672000). |
| Email of the user posting the event that triggered the webhook. | |
| $EVENT_MSG | Text of the event (e.g.: @webhook-url Sending to the webhook). |
| $EVENT_TITLE | Title of the event (e.g.: [Triggered] [Memory Alert]). |
| $EVENT_TYPE | Type of the event *(values: metric_alert_monitor, event_alert, or `service_check. |
| $HOSTNAME | The hostname of the server associated with the event, if there is one. |
| $ID | ID of the event (e.g.: 1234567). |
| $LAST_UPDATED | Date when the event was last updated. |
| $LINK | URL of the event (e.g.: https://app.datadoghq.com/event/jump_to?event_id=123456). |
| $LOGS_SAMPLE | Logs sample from log monitor alerts. |
| $METRIC_NAMESPACE | Namespace of the metric if it’s an alert. |
| $ORG_ID | ID of your organization (e.g.: 11023). |
| $ORG_NAME | Name of your organization (e.g.: Datadog). |
| $PRIORITY | Priority of the event (values: normal or low). |
| $SNAPSHOT | URL of the image if the event contains a snapshot (e.g.: https://url.to.snpashot.com/). |
| $TAGS | Comma-separated list of the event tags (e.g.: monitor, name:myService, role:computing-node). |
| $TEXT_ONLY_MSG | Text of the event without Markdown formatting. |
| $USER | User posting the event that triggered the webhook (e.g.: rudy). |
| $USERNAME | Username of the user posting the event that triggered the webhook. |
If you want to post your webhooks to a service requiring authentication, you can use basic HTTP authentication by modifing your URL from https://my.service.com to https://username:password@my.service.com.
In a monitor alert, if 2 or more webhook endpoints are notified, then a webhook queue is created on a per service level. For instance, if you reach out to PagerDuty and Slack, a retry on the Slack webhook does not affect the PagerDuty one.
However, in the PagerDuty scope, certain events always go before others—specifically, an “Acknowledge” payload always goes before “Resolution”. If an “Acknowledge” ping fails, the “Resolution” ping is queued due to the retry logic.
A service X webhook failure does not affect the webhook of service Y.
Datadog only issues a retry if there is an internal error (badly formed notification message), or if Datadog receives a 5XX response from the webhook endpoint. Missed connections are retried 5 times.
Use as URL:
https://{Your-Account-id}:{Your-Auth-Token}@api.twilio.com/2010-04-01/Accounts/{Your-Account-id}/Messages.json
and as a payload:
{
"To":"+1347XXXXXXX",
"From":"+1347XXXXXX",
"Body":"$EVENT_TITLE \n Related Graph: $SNAPSHOT"
}
Replace To with your phone number and From with the one Twilio attributed to you. Check the Encode as form checkbox.
Use as URL:
https://{Your-Jira-Username}:{Your-Jira-Password}@{Your-Domain}.atlassian.net/rest/api/2/issue
and as a payload:
{
"fields": {
"project": {
"key": "YOUR-PROJECT-KEY"
},
"issuetype": {
"name": "Task"
},
"description": "There's an issue. See the graph: $SNAPSHOT and event: $LINK",
"summary": "$EVENT_TITLE"
}
}Do not check the “Encode as form” checkbox.
On this page