DEVOPS
Weekly Noisy-Logger Digest: Rank Log Sources and Log Cleanups in Notion
Each week, ranks Axiom log sources by ingest and cost, attributes each to the deploys that changed its volume.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts the digest
- ActionQuery Axiom 7-day ingest + cost per log sourceAxiom
- ActionPull Vercel deploy history, attribute volume changesVercel
- LogicFilter to sources above cost floor, flag growth
- OutputUpsert ranked cleanup rows into Notion databaseNotion
What it does
Builds a weekly leaderboard of your costliest log sources and turns it into a living cleanup backlog in Notion. It connects each noisy source to the deploys that moved its volume, so prioritization is grounded in cause, not guesswork.
When to use it
Use it for steady-state cost governance rather than incident response. Good for platform teams that hold a weekly review and want a durable, ranked record of which loggers to trim next.
How it works
- 1A weekly schedule kicks off the digest run.
- 2It queries Axiom for ingest bytes and projected cost per log source over the trailing seven days, sorted descending.
- 3It pulls the week's Vercel deploy history and attributes each source's volume change to the deploys in its window.
- 4A logic step filters to sources above a cost floor and flags week-over-week growth.
- 5It upserts one row per flagged source into a Notion database with cost, trend, attributed deploys, and an owner, ready for triage.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect NotionPages, databases, comments.
- 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.