DEVOPS
Pre-release budget check on version tags with GitHub comment
When a release tag is pushed, queries Datadog for the service's remaining error budget and posts a go/no-go comment on the GitHub release with the budget number.
How it runs
The automated pipeline, trigger to output.
- TriggerRelease tag pushedGitHub
- ActionRead remaining budget + burn from DatadogDatadog
- LogicDecide go / caution / hold vs rollback reserve
- OutputComment recommendation on GitHub releaseGitHub
What it does
Adds a budget sanity check to the moment you cut a release. On a version tag push it asks Datadog how much error budget the service has left, decides whether that is enough to safely absorb a bad rollout plus rollback, and annotates the GitHub release with a clear go or hold recommendation.
When to use it
Use it when releases are tagged manually or by CI and you want a budget-aware second opinion attached right where engineers cut the release. Lighter than a hard freeze when you prefer human judgment with data.
How it works
- 1A GitHub tag push matching your release pattern triggers the flow.
- 2The flow reads the service's remaining SLO budget and recent burn rate from Datadog.
- 3A logic step decides go, caution, or hold based on whether budget exceeds your rollback-cost reserve.
- 4It posts a comment on the corresponding GitHub release or tag with the recommendation and the budget figure.
- 5The release author sees the verdict inline before promoting the build.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DatadogMetrics, traces, log search.
- 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
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.