DEVOPS
Cloudflare Cold-Start Anomaly to PagerDuty with Rollback Hint
Watches Datadog for cold-start latency anomalies on Cloudflare Workers, correlates the spike to the most recent deploy tag.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog cold-start anomaly alertDatadog
- ActionFind deploy tag live at spike startCloudflare
- LogicPage only if severe and sustained
- ActionOpen PagerDuty incident with rollback hintPagerDuty
- OutputPost Slack summary with graph and tagsSlack
What it does
When Datadog detects an anomaly in Cloudflare Worker cold-start latency, this workflow figures out which deploy tag was live when the spike began, decides whether the regression is severe and sustained enough to wake someone, and if so opens a PagerDuty incident enriched with the suspect tag and the previous known-good tag to roll back to.
When to use it
Use it for production Workers where cold-start latency directly affects user-facing response times and you need on-call paged with actionable context instead of a bare "latency high" alert. It removes the manual scramble of mapping a graph spike back to a release.
How it works
- 1A Datadog monitor on cold-start p99 fires its anomaly alert as the trigger.
- 2List recent Cloudflare deployments to find the tag active at the spike's start time.
- 3Branch: only proceed if the anomaly magnitude and duration clear the paging threshold.
- 4Open a PagerDuty incident with the suspect tag, baseline, and the prior good tag.
- 5Post a Slack summary linking the Datadog graph, the suspect tag, and the rollback target.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.