DEVOPS
Per-Deploy Log Regression Check: Comment the Offending PR on GitHub
After each Vercel production deploy, measures the new build's per-minute Axiom ingest rate against the previous deploy and, if it regressed sharply, posts a comment…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment-succeeded webhook firesVercel
- ActionQuery Axiom ingest-per-minute for new vs prior deployAxiom
- LogicStop unless rate increase exceeds regression threshold
- ActionBreak down Axiom volume to noisiest new log sourceAxiom
- OutputComment offending GitHub PR with delta + hygiene checklistGitHub
What it does
Catches log-volume regressions at the source: the pull request that introduced them. It measures each deploy's steady-state ingest rate, compares it to the prior deploy, and leaves the evidence as a PR comment so the author fixes it before it compounds.
When to use it
Use it when you want logging cost treated like a performance budget enforced in code review. Ideal for teams practicing trunk-based delivery where every deploy maps cleanly to a merged PR.
How it works
- 1A Vercel deployment-succeeded webhook triggers and the workflow waits a short settle window for traffic to normalize.
- 2It queries Axiom for the new deploy's ingest-per-minute rate and the prior deploy's rate over the same duration.
- 3A logic step compares the two; it stops if the increase is under the regression threshold.
- 4It runs an Axiom breakdown to find the log source or route contributing the most new volume.
- 5It maps the deploy's commit SHA to the GitHub PR and posts a comment with the rate delta, the noisy source, and a hygiene checklist.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect VercelDeploys, runtime logs, analytics.
- 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
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.