Monitoring & APM
Datadog
Pull Datadog monitor alerts and Events API alerts into incidents, reconcile host inventory into the CMDB, and push incident-lifecycle state back to Datadog as an event.
BidirectionalData residency: EU
Request a demoWhat it does
- monitor.alert and event.triggered → incident, with Datadog's P1–P5 priority mapped to platform severity (tenant override map supported, safe mid-severity fallback)
- host.inventory → CMDB CI reconciliation
- Incident lifecycle pushed back to Datadog as an event (state → alert_type: error/warning/success/info) so a Datadog dashboard reflects our handling
- Signed inbound webhooks (HMAC) alongside a scheduled poll of the Monitors + Events API
- Authenticates with a Datadog API key + Application key, not OAuth
Data residency
Catalog default is EU (datadoghq.eu). A tenant on a US site (datadoghq.com, US3, US5, AP1) is gated by a non-EU acknowledgement before the integration can be enabled — resolved per-tenant from the chosen site.
Event mappings
| External event | Maps to | What happens |
|---|---|---|
| monitor.alert | incident | A Datadog monitor entering alert creates an incident (severity from priority) |
| event.triggered | incident | A Datadog Events API alert (polled) reconciles into an incident |
| host.inventory | ci | Datadog host inventory reconciles into CMDB CIs |
What you configure
- Region (eu/us) and concrete site (datadoghq.eu, datadoghq.com, us3/us5/ap1)
- API key configured (flag only — the value is a secret)
- Application key configured (flag only)
- Webhook signing secret configured (flag only)
Setup overview
Point the integration at your Datadog site and store the API key + Application key as secrets. Configure a Datadog webhook for the signed inbound path, or rely on the scheduled poll.
Related features
See TENSOR running on your own estate.
30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.