SUMMARIZATION

Monthly Axiom Cost-Attribution Report by Email

On the first of each month, rolls up the prior month's Axiom log cost by service and by team owner, summarizes the headline movements.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule on the 1st
  • ActionQuery Axiom: prior month ingest by serviceAxiom
  • LogicMap services to owning teams; roll up by team
  • ActionWrite executive summary of cost movementsOpenAI
  • OutputEmail formatted report to stakeholdersGmailGmail

What it does

Produces a month-end observability cost report. It rolls up the prior calendar month of Axiom log ingest by service, maps each service to its owning team, summarizes the largest line items and month-over-month shifts, and delivers a clean formatted email to a stakeholder distribution list.

When to use it

Use it when log cost needs to land in inboxes for monthly business reviews, with attribution rolled up to teams that own budgets. It closes the loop between raw service metrics and the people accountable for spend.

How it works

  1. 1A monthly schedule trigger fires on the first of the month.
  2. 2Axiom is queried for the prior full month's ingest and events grouped by service.
  3. 3A logic step maps each service to its owning team using a configured ownership table and rolls costs up by team.
  4. 4An OpenAI step writes the executive summary: top teams, biggest movers, and notable new services.
  5. 5A Gmail step sends the formatted report to the stakeholder list.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AxiomLog streams, queries, dashboards.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.