DEVOPS
Datadog p99 Tail Spike to PagerDuty Scaling Runbook
When Datadog detects a p99 latency spike that correlates with a saturation metric, this workflow pages on-call via PagerDuty with a pre-filled scaling runbook and the exact…
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog p99 latency spike monitor firesDatadog
- ActionQuery Datadog CPU and queue-depth saturation metricsDatadog
- LogicConfirm saturation is the cause; exit if downstream dependency
- ActionCompute recommended replica count from utilization headroom
- OutputOpen PagerDuty incident with scaling runbookPagerDuty
What it does
Detects a p99 tail-latency spike in Datadog, confirms it is driven by resource saturation (not a downstream dependency), and pages the on-call engineer through PagerDuty with a ready-to-run scaling runbook that already contains the recommended replica count and the evidence behind it.
When to use it
Use it for latency-sensitive services where p99 regressions need a fast, decisive human response. The saturation check prevents false pages when slowness comes from an upstream API rather than your own capacity.
How it works
- 1A Datadog monitor fires on a p99 latency spike for the service.
- 2The flow queries Datadog for CPU and queue-depth saturation over the same interval.
- 3A logic branch confirms saturation is the cause; if the bottleneck is a downstream dependency, it exits without paging.
- 4It computes a recommended replica count from current utilization and headroom targets.
- 5It opens a PagerDuty incident with the runbook, recommendation, and metric links attached.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.