Datadog Webhook Integration

Forward Datadog alerts to any system with on-call in between.

Alert ⚠️

Forward

Alert ⚠️

Forward

The Datadog webhook integration forwards Datadog monitor alerts to your own HTTP endpoint through All Quiet. Datadog sends each alert to an All Quiet webhook. All Quiet creates an incident, notifies the on-call engineer, escalates if nobody responds and sends a request to your endpoint for each incident event, such as creation, comments and resolution. You define the method, URL, headers and body.

Start free trial

How the Datadog Webhook integration works

1

In All Quiet, open Inbound Integrations, click + Create, choose Datadog as the type, select a team and copy the webhook URL.
2

In Datadog, open Integrations, install the Webhooks integration and click New Webhook in the Configuration tab. Enter a name, paste the All Quiet webhook URL and the payload from the Datadog setup guide, then save.
3

In each monitor, add @webhook- followed by your webhook name under "Configure notifications & automations", and set the monitor's priority in the Metadata section.
4

In All Quiet, open Outbound Integrations, click + Create, choose Webhook and pick a forwarding setting.
5

In the template section, load a test incident and write a Handlebars template for the method, URL, headers and body. Optionally choose a signing method and enter a signing secret.
6

Click Trigger Dummy Request and check the request and response under Latest Requests.

Full guides: Datadog setup guide Webhook setup guide

What you get

Repeated Datadog alerts grouped into one incident
Requests you define: method, URL, headers and body
On-call and escalation before anything is forwarded

Use cases

Open a record in an internal tool.

Your endpoint receives a request when the incident opens and again for each later event, so an internal ticketing or tracking system stays in step with the incident without anyone copying details across.

Send only the fields your tool needs.

The Handlebars template reads incident attributes by name, so the request body can carry exactly the fields your system expects, in its format, rather than Datadog's raw payload.

Trigger automation after on-call is involved.

Start a runbook or a diagnostic job when the incident opens. If your endpoint returns a valid patch response and the template enables incident updates, it can update the incident in All Quiet.

FAQ

How do I connect Datadog to Webhook?

Create an inbound integration for Datadog in All Quiet and add its webhook URL in Datadog. Then create an outbound integration for Webhook. The Datadog setup guide and the Webhook setup guide on docs.allquiet.app walk through each step.

What does All Quiet add between Datadog and Webhook?

All Quiet turns each Datadog alert into an incident, notifies the engineer on call, escalates if nobody responds and keeps a record of the incident. Webhook receives the incident with that context.

Can I try the Datadog Webhook integration for free?

Yes. Start a free trial of All Quiet and connect Datadog and Webhook during the trial.

Where is my data hosted?

All Quiet is a European incident management platform: built in Berlin, with selectable EU data residency in Frankfurt, GDPR compliance, and ISO 27001 certification. Alert data for EU customers is stored and processed in Frankfurt. That matters for on-call specifically because alert and escalation data routinely contains production system details.

What does the outgoing webhook request contain?

Whatever your template defines. The outbound webhook uses a Handlebars template with a method, a URL, headers and a body as JSON, form data or text. Incident attributes are available by name with attributesByName followed by the attribute name. Requests can be signed with HMAC-SHA256 so your endpoint can verify them.

Why not send the Datadog webhook straight to my endpoint?

You can: Datadog's Webhooks integration posts monitor alerts to any URL with a custom payload and headers. Routing through All Quiet adds on-call in between. The alert becomes an incident, the on-call engineer is notified, it escalates if nobody responds, and your endpoint also receives later events such as comments and resolution.