SUMMARIZATION
Axiom + Honeycomb Cross-Source Reliability Brief
Pulls the week's top error patterns from Axiom and matching latency/trace spikes from Honeycomb, correlates them, and writes a single brief that explains which log patterns…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch top Axiom error signaturesAxiom
- ActionFetch Honeycomb latency + slow-trace spikesHoneycomb
- LogicCorrelate errors to performance impact
- ActionWrite correlated reliability briefOpenAI
- OutputSave dated page to NotionNotion
What it does
Most reliability summaries report logs and traces separately, leaving humans to guess which noisy error actually slowed users down. This template joins both: it takes Axiom's top error patterns and Honeycomb's latency outliers for the same week, lines them up by service and time window, and produces one brief that says which log patterns coincided with real performance pain — and which were harmless chatter.
When to use it
Use it when you run Axiom for logs and Honeycomb for tracing and want a weekly verdict on what mattered, not two dashboards to reconcile by hand.
How it works
- 1A weekly schedule trigger kicks off the run.
- 2An Axiom action returns the top error signatures with counts.
- 3A Honeycomb action returns p95 latency and slow-trace spikes per service for the same window.
- 4A logic step correlates the two sets by service and overlapping time, tagging each error pattern as user-impacting or benign.
- 5An OpenAI action drafts a correlated reliability brief in plain English.
- 6A Notion output saves it as a dated page in the reliability log.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.