SUMMARIZATION
Honeycomb SLO-burn alert enriched with a plain-English root-cause trace story
When a Honeycomb SLO-burn alert fires, it pulls the worst offending trace, summarizes the latency cause in plain English.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb SLO-burn alert webhook firesHoneycomb
- ActionFetch the exemplar trace span waterfallHoneycomb
- LogicIsolate critical-path span and measure budget impact
- ActionWrite a plain-English root-cause storyOpenAI
- OutputAttach the story as a note on the PagerDuty incidentPagerDuty
What it does
When Honeycomb signals that a latency SLO is burning fast, this workflow grabs the trace driving the breach, summarizes its waterfall into a plain-English root-cause story, and writes that story straight onto the PagerDuty incident. The on-call engineer opens the page already knowing which step is slow instead of starting from a raw alert.
When to use it
Use it for latency SLOs where every minute of triage matters. It removes the first painful step of an incident — reconstructing what the trace is telling you — by handing responders a ready summary.
How it works
- 1A Honeycomb SLO-burn webhook fires and includes the triggering query and exemplar trace.
- 2The workflow fetches that exemplar trace's full span waterfall from Honeycomb.
- 3A logic step isolates the critical-path span and compares its duration to the SLO budget.
- 4OpenAI writes a tight root-cause story: the slow step, the service it lives in, and how much of the budget it consumed.
- 5The summary is posted as a note onto the matching PagerDuty incident, with the trace link for deep-diving.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.