SUMMARIZATION
Slow-span cluster to latency regression brief in Slack
On a Honeycomb trigger board firing, groups the slowest spans by service and operation, then posts a plain-English latency regression brief to your perf Slack channel.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb latency trigger firesHoneycomb
- ActionQuery slowest spans in trigger windowHoneycomb
- LogicCluster spans by service + operation, score contribution
- LogicExit if no cluster exceeds materiality floor
- ActionSummarize top clusters into latency briefOpenAI
- OutputPost brief with Honeycomb deep link to perf channelSlack
What it does
When a Honeycomb latency trigger fires, this workflow pulls the offending traces, clusters the slowest spans by service and operation name, and writes a concise narrative explaining which calls regressed, by how much, and against what baseline. The brief lands in your performance Slack channel so engineers read a story, not a wall of percentiles.
When to use it
Use it when your team gets paged by raw Honeycomb triggers that say "p99 over threshold" but force everyone to open the UI and hunt for the cause. This turns the alert into an actionable summary the moment it fires.
How it works
- 1A Honeycomb trigger crosses its p99 latency threshold and fires the webhook.
- 2The workflow queries Honeycomb for the slowest spans in the trigger window.
- 3It clusters spans by `service.name` + `name`, computing each cluster's contribution to the regression.
- 4If no cluster exceeds the materiality floor, the run exits quietly.
- 5An LLM turns the top clusters into a plain-English brief naming the likely culprit operation and its delta vs. baseline.
- 6The brief posts to the perf Slack channel with a deep link back to the Honeycomb query.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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…
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.
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.
Escalate blockers from Loom standups to Slack
Transcribes each new Loom standup video, uses AI to detect blockers and dependencies.
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.