DEVOPS
Datadog Alert to PagerDuty On-Call Triage
When a Datadog monitor fires, classify the alert by severity and service, page the right on-call rotation in PagerDuty, and open a triage thread in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog monitor alert receivedDatadog
- LogicClassify severity and resolve owning on-call team
- LogicDrop low-priority warnings, escalate P1/P2
- ActionCreate PagerDuty incident on matched escalation policyPagerDuty
- OutputOpen Slack triage thread tagging responderSlack
What it does
Turns a raw Datadog monitor alert into a routed, paged incident. It reads the alert's tags and priority, decides which team owns the affected service, and creates a PagerDuty incident on that team's escalation policy. It then opens a dedicated Slack thread so responders coordinate in one place instead of hunting through alert noise.
When to use it
Use this as the front door for production alerting when you have multiple services and on-call rotations and want every Datadog alert to reach exactly the right human within seconds, with full context attached.
How it works
- 1A Datadog monitor crosses its threshold and posts the alert webhook.
- 2Logic inspects the alert priority and `service`/`team` tags to pick a severity tier and owning rotation.
- 3Low-priority warnings are filtered out and only logged; P1/P2 alerts proceed.
- 4A PagerDuty incident is created against the matched escalation policy with the alert title, runbook link, and Datadog graph URL.
- 5A Slack message opens an incident thread tagging the paged responder and linking the PagerDuty incident for live coordination.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.