ENGINEERING
Axiom Noisy Log Stream Detector with Auto-PR
Each morning scans Axiom for log streams with abnormally high event volume and low diagnostic value, then opens a GitHub PR that raises their log level from debug/info to warn.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery Axiom for per-stream event volumeAxiom
- LogicKeep high-volume low-signal streams
- ActionLocate emitting log call sites in repoGitHub
- OutputOpen PR raising log levelsGitHub
What it does
Finds the log lines that are drowning out everything useful and quiets them at the source. It ranks Axiom datasets by event count, flags the chatty ones whose messages are repetitive boilerplate (heartbeats, polling ticks, cache hits), and drafts a code change that bumps those loggers to a higher level.
When to use it
Run it when your Axiom bill is climbing, dashboards are sluggish, or on-call keeps scrolling past walls of identical lines. Best as a scheduled daily hygiene pass so noise never compounds.
How it works
- 1A daily schedule fires the workflow.
- 2It queries Axiom for per-dataset and per-message-template event counts over the last 24 hours.
- 3A logic step keeps only streams above the volume threshold whose top message templates carry low signal (low cardinality, no error keywords).
- 4For each flagged logger it locates the emitting call site in the GitHub repo and rewrites the level (e.g. `logger.info` to `logger.debug`).
- 5It opens a GitHub pull request with the before/after volume estimate and a per-logger diff for review.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.