DEVOPS
Axiom Ingest Spike: Find the Chatty Deploy and Open a Hygiene Task
When Axiom log ingest jumps above its rolling baseline, this workflow correlates the spike to the most recent Vercel deploy, identifies the noisiest dataset.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires the ingest check
- ActionPull last-hour ingest bytes per dataset from AxiomAxiom
- LogicExit unless ingest exceeds 7-day baseline by 50%
- ActionList Vercel deploys in the spike window, pick latest prodVercel
- ActionRank Axiom datasets by growth, grab top offender + sampleAxiom
- OutputOpen Linear logging-hygiene task assigned to deploy authorLinear
What it does
Watches Axiom ingest volume and reacts when a sudden jump threatens your log bill. It pinpoints which deploy started the bleed, names the chattiest log source, and files an actionable cleanup task instead of just paging someone.
When to use it
Use it when your Axiom spend is unpredictable and spikes usually trace back to a deploy that left debug logging on or added a hot log line. Good for teams that ship to Vercel many times a day and want cost discipline without manual log audits.
How it works
- 1A scheduled check pulls the last hour of Axiom ingest bytes per dataset.
- 2A logic step compares the total to a 7-day rolling baseline; it exits quietly unless ingest is more than 50 percent above baseline.
- 3On a spike, it queries Vercel for deployments in the spike window and selects the most recent production deploy as the likely cause.
- 4It runs an Axiom query to rank datasets by ingest growth and grabs the top offender plus a sample line.
- 5It opens a Linear task tagged logging-hygiene with the deploy SHA, dataset, projected daily cost, and sample, assigned to the deploy author.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.