SUMMARIZATION

Weekly Axiom Log-Pattern Reliability Note

Every Monday, pulls the past week of Axiom logs, clusters them into recurring error patterns.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery Monday 8am
  • ActionQuery last 7 days of logs by signatureAxiom
  • LogicDrop low-volume noise, flag rising patterns
  • ActionSummarize clusters into plain-English noteOpenAI
  • OutputPost reliability note to DiscordDiscordDiscord

What it does

Turns a week of raw Axiom logs into a short, plain-English reliability note that anyone can read. It groups noisy log lines into a handful of recurring patterns, ranks them by how often they fired and whether they got worse, and explains each one in one sentence — no query language, no stack traces.

When to use it

Run it as a Monday-morning ritual when your team drowns in log volume but leadership and support still ask "was last week healthy?" It replaces the manual habit of one engineer skimming dashboards and paraphrasing them in chat.

How it works

  1. 1A scheduled trigger fires every Monday at 8am.
  2. 2An Axiom action runs an aggregating APL query over the last 7 days, returning error counts bucketed by message signature.
  3. 3A logic step drops patterns under a noise threshold and flags any whose week-over-week count rose more than 25%.
  4. 4An OpenAI action rewrites the surviving clusters into a ranked, plain-English digest with a one-line health verdict.
  5. 5A Discord output posts the note to your reliability channel.

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 DiscordCommunity channels + voice + bots.
  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.