SUMMARIZATION
Honeycomb Latency Regression to Linear Triage Tickets
On a daily run, detects services whose p95 latency regressed beyond a threshold versus the prior week in Honeycomb, summarizes the likely cause with OpenAI.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule triggers the run
- ActionFetch per-service p95 latency vs prior-week baselineHoneycomb
- LogicKeep only regressions past threshold
- ActionSummarize likely cause and affected operationsOpenAI
- OutputOpen triage ticket in LinearLinear
What it does
Compares each service's p95 latency over the last 24 hours against its prior-week baseline pulled from Honeycomb. When a service crosses the regression threshold, it writes an investigation-ready summary and files a Linear ticket. Services within normal variance are skipped, so the backlog stays signal-only.
When to use it
Use it when latency creep slips through code review and you want regressions to become tracked work automatically instead of relying on someone noticing a slow dashboard line.
How it works
- 1A daily schedule triggers the run.
- 2Honeycomb returns per-service p95 latency for the last day plus the prior-week baseline.
- 3A logic step keeps only services whose regression exceeds the configured percentage threshold.
- 4OpenAI drafts a concise summary: which service, how much it slowed, and candidate operations driving the change.
- 5A Linear ticket is created in the triage project with the summary and a 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 LinearIssues, projects, cycles, triage.
- 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.