APM & tracing

Send Datadog alerts to on-call with CallHeim.

Monitors & events via Datadog webhook integration. CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.

datadogsource names also accepted: dd, datadoghq

Set the payload template first

Datadog posts to your CallHeim URL, but it only sends the fields you put in its payload template. Without one it sends an empty or differently shaped body that CallHeim cannot map, so set the template described in the setup steps before you point an alert at this integration.

Datadog monitor alerts become CallHeim alerts: repeats of the same monitor collapse onto one incident, and the service the monitor is bound to pages whoever is on call for it. CallHeim includes a payload mapping for Datadog’s webhook format.

How the alert reaches on-call

  1. Step 1A Datadog monitor changes state and renders your webhook payload template.
  2. Step 2Datadog POSTs the rendered JSON body to your CallHeim ingest URL over HTTPS.
  3. Step 3CallHeim reads alert_id plus the monitor group (alert_scope, or the group in the alert title) as the identity signal, maps priority or alert_type to a severity, and reads alert_transition to tell a recovery from a trigger.
  4. Step 4A repeat of the same monitor group attaches to the incident that is already open for it.
  5. Step 5The integration's bound service selects an escalation policy, which pages the on-call tier.

Setting it up

  1. 01

    Create the webhook in Datadog first, with a custom payload.

    Datadog's default webhook body is empty; the integration only receives usable fields when you supply a payload template yourself, in Integrations > Webhooks.

  2. 02

    Name the webhook and enter your CallHeim ingest URL.

    Create the Datadog integration in CallHeim first so you have the exact ingest URL to paste in.

  3. 03

    Set the payload template to include alert_id, alert_title, alert_type, alert_transition, alert_scope, priority, event_msg and tags.

    These are the fields the CallHeim parser reads. alert_transition is what marks a Recovered notification; alert_scope keeps each group of a multi-alert monitor separate. Omitting alert_id means repeats are grouped by title and tags instead of the monitor identity.

  4. 04

    Reference the webhook from a monitor.

    Add @webhook-<name> to the monitor's notification message so state changes call it.

Example payloadJSON
{
  "alert_id": "1234567",
  "alert_title": "[Triggered on {host:web-1}] High error rate on web-store",
  "alert_type": "error",
  "alert_transition": "Triggered",
  "alert_scope": "host:web-1",
  "priority": "normal",
  "event_msg": "error rate is 12% (> 5%) on service:web-store env:prod",
  "tags": "service:web-store,env:prod"
}
Example payload in the fields the template asks Datadog to send; check Datadog's own documentation for the full variable list.

What CallHeim reads from the payload

Payload fields and what each one maps to on the incident
Payload fieldMaps toNote
alert_title / title / event_titleincident titleFirst one present wins; falls back to "Datadog alert".
priority (P1–P5)severityUsed only when it holds a P1–P5 value. The template's $PRIORITY is Datadog's event priority (normal or low), which does not map, so severity then comes from alert_type. Send $ALERT_PRIORITY in this field to use the monitor's own P1–P5 priority.
alert_type (error / warning / success / info / no_data)severityUsed when priority holds no P1–P5 value: error→P1, warning→P3, success, info and no_data→P4.
event_msg / body / text_only_msg / messageincident body
alert_id + alert_scopeidentity signalThe monitor plus its group, so each group of a multi-alert monitor is its own alert. When alert_scope is missing, the group is taken from the title prefix Datadog adds ("[Recovered on {host:web-1}] …"). The identity is the same for a trigger and its recovery.
alert_transitionlifecycleRecovered resolves the alert for that monitor group; any other value is treated as a trigger.

How CallHeim processes it

Routing

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged.

Deduplication

A repeat of the same alert attaches to the incident that is still open for it in the same service, triggered or acknowledged, with no new incident and no new page. When the sender supplies its own dedup key (a PagerDuty dedup_key, an Opsgenie alias, a Datadog alert id, an Alertmanager fingerprint, or a dedupKey that is more than the alert title), this holds however late the repeat arrives. When the identity comes from the e-mail subject or the alert title, the repeat attaches only if the incident was triggered in the last 24 hours; after that it opens a new incident and pages. A repeat at P1 or P2 is not folded into an open P3, P4 or P5 incident: it opens a new incident and pages. Once an incident is resolved or closed, the next repeat opens a new incident. For Datadog, the fingerprint is keyed on alert_id plus the monitor group when your template sends alert_id (falling back to the title plus tags), so repeated firings of the same monitor group collapse and a different monitor or group never does. The alert id is Datadog's own key, so a repeat attaches at any age; the title-plus-tags fallback is a title identity, so the 24-hour limit applies to it.

Recovery

When Datadog sends a Recovered notification, CallHeim resolves the alert for that monitor group; an incident holding several groups closes when the last one recovers. This needs alert_transition in the payload template (and alert_scope for a multi-alert monitor). Checked on 26 September 2026 with webhooks in this template's format, sent by a test script rather than by a Datadog account.

Troubleshooting

Common problems and how to fix them
ProblemFix
The alert arrives with no title or body.Datadog's default webhook body is empty. Set a custom payload template on the webhook (see setup) before pointing a monitor at it.
A recovered monitor does not close the incident.Check that the payload template sends alert_transition, and alert_scope for a multi-alert monitor. An incident that holds several groups stays open until the last one recovers.
HTTP 400 on send.The payload template is not valid JSON once Datadog substitutes its variables — check for an unescaped quote inside $EVENT_MSG.
HTTP 401 once you enabled signing.Datadog cannot send a signature computed for each request. Remove the signing secret from this integration, or put a proxy you run in front that signs each request.
Every Datadog alert lands as P3.Neither priority nor alert_type was present in the delivered body — check the payload template was saved on the webhook, not just on the monitor.
Repeats open a second incident.The earlier incident had already been resolved or closed, or alert_id was missing from the template so the fallback title+tags signal changed between events, or, with that fallback, the open incident was triggered more than 24 hours ago. A P1 or P2 repeat on an open P3 to P5 incident also opens a new incident.

Security

Datadog's webhook can send only fixed custom headers, which cannot carry a signature computed for each request. The integration URL is the credential: keep it secret, and if it is exposed, disable the integration and create a new one. A signing proxy you run in front of the sender can add an X-CallHeim-Signature header; without one, do not set a signing secret, because every unsigned delivery would be rejected.

Vendor documentation checked

The thresholds it passes through

Repeat, sender-supplied dedup key
attaches, any age
Repeat, title or subject only
attaches, incident under 24 h old
Flap threshold
4 transitions / 600s
Title correlation
similarity ≥ 0.6, same source and service
Group window default
600s

All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →

CallHeim

Point Datadog at CallHeim and see what it does with your alerts.

Start on the free trial, connect Datadog and send a test alert to see the incident it opens.