AI AGENTS
Axiom log correlation for CDN cost root-cause
On a daily run, an agent queries Axiom request logs to find which route saw an abnormal jump in cache-miss volume, correlates it to the deploy or referrer that triggered it.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled analysis
- ActionQuery per-route cache-miss counts (Axiom APL)Axiom
- LogicKeep routes above anomaly multiplier
- ActionPull first-seen and top referrers per route (Axiom)Axiom
- ActionRank drivers and draft cache rulesOpenAI
- OutputPost ranked cost-driver report to SlackSlack
What it does
Uses your Axiom request logs as the source of truth to explain a CDN cost jump. It finds routes whose cache-miss count surged day-over-day, ties the surge to a specific deploy timestamp or top referrer, and proposes the cache change that would have absorbed it.
When to use it
When you ship logs to Axiom and want log-grounded attribution of a cost spike (which path, since when, driven by whom) rather than aggregate CDN counters that hide the cause.
How it works
- 1A scheduled trigger runs the daily analysis.
- 2The agent runs an Axiom APL query for per-route cache-miss counts and bytes over the last two days.
- 3A logic step keeps only routes whose miss volume rose beyond the anomaly multiplier.
- 4A follow-up Axiom query pulls the first-seen timestamp and top referrers for each flagged route to pin the trigger (a deploy, a scraper, a new embed).
- 5An OpenAI step ranks drivers by wasted bytes and drafts a cache rule per offender.
- 6The ranked report posts to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.