SUMMARIZATION
Weekly Error-Budget Burn Brief to Confluence
Every Monday, pulls the past week's SLO burn and slowest traces from Honeycomb, then publishes a plain-English reliability brief to Confluence that a product or exec audience can…
How it runs
The automated pipeline, trigger to output.
- TriggerMonday 7am schedule
- ActionQuery Honeycomb 7-day SLO burn + slow tracesHoneycomb
- LogicCompare against prior week, label trend per service
- ActionDraft plain-English reliability briefOpenAI
- OutputPublish dated brief to Confluence Reliability spaceConfluence
What it does
Turns a week of Honeycomb telemetry into a one-page reliability brief written for non-engineers. It reports how much of each service's error budget was consumed, what the worst latency offenders were, and whether the trend is improving or degrading — no PromQL or trace jargon required.
When to use it
Run it as a standing Monday-morning ritual when leadership, product, or customer-success teams keep asking "are we reliable right now?" and you're tired of translating dashboards by hand. Ideal for orgs that report reliability up the chain weekly.
How it works
- 1A Monday 7am schedule fires the workflow.
- 2It queries Honeycomb for the trailing 7-day SLO burn rate and the slowest long-running traces per service.
- 3An LLM step compares this week's burn against last week's to label each service trending up, flat, or down.
- 4The same step drafts a plain-English brief: budget remaining, top three slow paths in human terms, and a one-line verdict.
- 5The brief is published as a new Confluence page under the Reliability space, dated for the week.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.