ENGINEERING
Triage Honeycomb p99 latency outliers into a Linear perf ticket
On a schedule, queries Honeycomb for the slowest spans in a service, identifies the offending database query.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionQuery Honeycomb for spans above p99 threshold, grouped by queryHoneycomb
- LogicPick top offender; skip if under SLO
- ActionSearch Linear for an existing ticket with this query fingerprintLinear
- ActionCreate Linear perf ticket with query, metrics, and trace linkLinear
- OutputPost ticket link to Slack perf channelSlack
What it does
Every hour it pulls the worst-offending spans from a Honeycomb dataset, isolates the specific operation and query driving p99 latency, and opens a Linear performance ticket scoped to that query — only if one does not already exist.
When to use it
When a service has intermittent latency spikes and you want them turned into actionable, owner-assigned tickets instead of dashboards nobody watches. Best for teams who triage perf in Linear and want the slow query and a trace exemplar in the ticket body.
How it works
- 1A schedule fires hourly.
- 2Query Honeycomb for spans in the target dataset where duration exceeds the p99 threshold, grouped by `db.statement` and `name`.
- 3A logic step filters to the top offender and skips runs where the slowest span is under the SLO.
- 4Search Linear for an open ticket matching the query fingerprint to avoid duplicates.
- 5If none exists, create a Linear issue with the query text, p99/p50 numbers, span count, and a direct Honeycomb trace link.
- 6Post the new ticket link to the team's Slack perf channel.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect LinearIssues, projects, cycles, triage.
- 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 Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
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.