ENGINEERING
Pinpoint the deploy that slowed a query and open a Linear issue
When a Honeycomb trigger fires on rising query latency, this correlates the regression window against recent GitHub deploys, identifies the most likely offending PR.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb latency trigger firesHoneycomb
- ActionFetch slow trace and regression window from HoneycombHoneycomb
- ActionList GitHub deploys and merged PRs in the windowGitHub
- LogicRank suspect PRs by deploy proximity and touched code path
- OutputOpen Linear issue with trace and top suspect PRLinear
What it does
Turns a Honeycomb latency alert into a named suspect. It pulls the slow trace, lines up the regression start against recent merges, and hands engineering a Linear issue that already points at the probable culprit PR — no manual archaeology.
When to use it
Run this whenever a service has a Honeycomb trigger watching p95/p99 on a query or endpoint and you want the on-call engineer to get a ranked suspect instead of a bare "latency is up" page.
How it works
- 1A Honeycomb trigger fires when query latency crosses its threshold and posts the trace and the regression window.
- 2The flow queries Honeycomb for the exemplar slow trace and the timestamp latency first stepped up.
- 3It pulls GitHub deploys and merged PRs that landed inside that window.
- 4A decision step ranks candidates by deploy time proximity and whether the PR touched the query's code path or migrations.
- 5It creates a Linear issue with the trace link, the regression timestamp, and the top suspect PR linked.
- 6The issue is assigned to the PR author's team for fast triage.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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 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.