DEVOPS
Post-Deploy Regression Watch With Auto-Rollback Alert
After a deploy webhook fires, it watches Datadog error and latency metrics for a baseline window.
How it runs
The automated pipeline, trigger to output.
- TriggerDeploy finished (incoming webhook)HTTP webhook
- ActionRecord pre-deploy metric baselineDatadog
- ActionRe-query metrics after soak windowDatadog
- LogicDetect regression vs. baseline + tolerance
- OutputPage on-call with rollback recommendationPagerDuty
What it does
This workflow closes the deploy-risk loop after release: it captures the pre-deploy baseline, watches the service for a set window, and if error rate or latency regresses against that baseline it pages the on-call engineer with a rollback recommendation and the offending metrics.
When to use it
Use it when bad deploys are caught too late — you want an automatic comparison of after-vs-before so a regressing release surfaces in minutes, not in the next customer ticket.
How it works
- 1A deploy-finished webhook fires with the service and version.
- 2A Datadog step records the pre-deploy baseline error rate and latency.
- 3The flow waits a defined soak window, then re-queries the same metrics.
- 4A logic step compares post-deploy values against the baseline plus tolerance.
- 5A branch fires only when a regression is detected.
- 6PagerDuty pages on-call with the regression details and a rollback recommendation.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.