SUMMARIZATION
Weekly Axiom Cost-by-Service Digest to Slack
Every Monday, aggregates the past week of Axiom log volume per service, summarizes the cost drivers in plain English, and posts a ranked digest to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery Monday 8am schedule
- ActionQuery Axiom: bytes + events by service, last 7dAxiom
- ActionQuery Axiom: prior 7d for week-over-week deltaAxiom
- ActionSummarize cost drivers and moversOpenAI
- OutputPost ranked digest to Slack channelSlack
What it does
Pulls the last seven days of log-stream data from Axiom, attributes ingest volume and estimated cost to each emitting service, then writes a short narrative summary of where the money went and which services moved the most week-over-week. The result lands in a Slack channel as a ranked, skimmable digest.
When to use it
Use it when your observability bill is opaque and you want a recurring, no-effort readout of which services drive log spend. Ideal for platform and infra teams who review cost in a Monday standup and need the story, not just a dashboard.
How it works
- 1A scheduled trigger fires every Monday morning.
- 2An Axiom query rolls up ingested bytes and event counts grouped by `service` over the trailing 7 days.
- 3The same query window is run for the prior week to compute deltas.
- 4An OpenAI step turns the numbers into a plain-English summary: top spenders, biggest movers, and one likely cause per outlier.
- 5A Slack message posts the ranked table plus the narrative to your chosen channel.
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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.