Datadog monitor fires.
Runframe incident exists.
Paste one webhook URL in Datadog. Every monitor alert becomes a structured incident with severity, service, and alert context attached. Setup takes 2 minutes.
How it works
Three steps. Nothing to install or maintain.
Copy your webhook URL
Open the service you want to monitor in Runframe. Copy the unique webhook endpoint from service settings. One URL per service.
Paste it in Datadog
In Datadog, go to Integrations, then Webhooks. Create a new webhook and paste your Runframe URL. No authentication tokens or custom payloads required.
Monitors fire, incidents appear
When a monitor transitions to alert state, Datadog POSTs to Runframe. An incident is created with severity, service, and full monitor context. No manual triage.
What the integration does
Runframe uses everything Datadog sends.
Automatic severity mapping
Datadog P1 becomes SEV0, P2 becomes SEV1, and so on down to P5. A critical monitor fires, Runframe opens a SEV0 incident. You never have to classify severity by hand.
Service correlation
Each webhook URL belongs to a specific service. When an alert comes in, Runframe pages the on-call team for that service. No routing rules to write.
Full alert context attached
Monitor name, message, tags, and transition state are captured on the incident at creation. Responders open the incident and already know what fired and why.
Auto-resolve on recovery
When a Datadog monitor recovers, it sends a resolution event to the same webhook. Runframe closes the incident and logs the recovery on the timeline. Nothing to clean up manually.
What gets mapped
Datadog monitor priority maps to Runframe severity levels.
Monitor name, message body, and tags are attached to the incident as context. Recovery events from Datadog automatically resolve the open incident.
Frequently asked questions
Connect Datadog in under 2 minutes.
Free plan available. No credit card required.