DEVOPS
Pre-Deploy Error-Rate Baseline Check With Datadog
Before a deploy job runs, it queries Datadog for the current error rate and latency of the target service and blocks or warns if the service is already degraded.
How it runs
The automated pipeline, trigger to output.
- TriggerPre-deploy check requested (incoming webhook)HTTP webhook
- ActionQuery current error rate and latencyDatadog
- LogicCompare metrics to healthy baseline
- LogicDecide allow vs. block deploy
- OutputReturn decision to CI and notify SlackSlack
What it does
This workflow runs as a pre-deploy gate: it asks Datadog whether the target service is currently healthy and returns a clear allow or block decision to your CI pipeline so deploys onto an already-degraded service get stopped automatically.
When to use it
Use it when deploys sometimes land while a service is mid-incident, making it impossible to tell whether the new release or the existing problem caused the next page.
How it works
- 1The CI deploy job calls an incoming webhook with the service name and environment.
- 2A Datadog step queries the last 15 minutes of error rate, p95 latency, and saturation metrics.
- 3A logic step compares each metric against its healthy baseline.
- 4A branch returns allow when all metrics are nominal, or block when any breaches.
- 5The decision and the breaching metric are posted to Slack and returned in the webhook response for CI to act on.
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 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
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.