DEVOPS
Deploy Latency Regression to GitHub Scaling Issue
After a deploy, this workflow compares post-deploy p95 latency against the pre-deploy baseline in Datadog and, on a confirmed regression.
How it runs
The automated pipeline, trigger to output.
- TriggerDeploy webhook received with release idHTTP webhook
- ActionQuery Datadog post-deploy vs pre-deploy p95 after stabilizationDatadog
- LogicBranch on regression exceeding threshold; exit if within budget
- ActionCompute interim scaling recommendation to hold SLO
- OutputOpen GitHub issue linking deploy, metrics, and recommendationGitHub
What it does
Triggered by a deploy webhook, it waits for a stabilization window, then compares post-deploy p95 latency against the pre-deploy baseline in Datadog. If latency regressed beyond the threshold, it opens a GitHub issue that ties the regression to the specific deploy and includes a recommended interim scaling change to absorb the new cost-per-request.
When to use it
Use it to catch deploys that quietly raise per-request latency and force you to over-scale. It gives the owning team a documented, actionable issue instead of a vague alert, with both the code suspect and the capacity workaround in one place.
How it works
- 1A deploy webhook triggers the flow with the new release identifier.
- 2The flow waits for a stabilization window, then queries Datadog for post-deploy vs. pre-deploy p95.
- 3A logic branch checks whether the regression exceeds the threshold; if not, it exits.
- 4It computes the interim scaling recommendation needed to hold the SLO at the new latency.
- 5It opens a GitHub issue linking the deploy, the regression metrics, and the 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 GitHubRepos, issues, pull requests, actions.
- 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.