ENGINEERING
Detect N+1 query patterns in Honeycomb and page when SLO burns
Scans Honeycomb traces for repeated identical queries within a single request, and if the resulting latency burns the service SLO it pages via PagerDuty and files a GitHub issue…
How it runs
The automated pipeline, trigger to output.
- Trigger30-minute schedule fires
- ActionQuery Honeycomb for repeated queries per traceHoneycomb
- LogicFlag N+1 traces; compute SLO burn from added latency
- ActionIf burning SLO, trigger PagerDuty incidentPagerDuty
- OutputElse file GitHub backlog issue tagged n+1GitHub
What it does
Periodically inspects Honeycomb traces for N+1 patterns — the same query executed many times inside one request — calculates the latency cost, and escalates only when that cost is burning the service error budget.
When to use it
When ORM-driven N+1 queries are your recurring perf killer and you want them caught automatically with severity tied to SLO impact, not just logged. Ideal for teams with a PagerDuty rotation who only want to be paged for real budget burn.
How it works
- 1A schedule fires every 30 minutes.
- 2Query Honeycomb for traces grouped by `trace.trace_id`, counting repeated `db.statement` values per trace.
- 3A logic step flags traces where one query repeats above the N+1 threshold and computes aggregate added latency against the SLO budget.
- 4If the SLO burn rate is breached, trigger a PagerDuty incident with the call site and repeat count.
- 5Otherwise, open a GitHub issue tagged `n+1` with the query, repeat count, and a trace link for backlog triage.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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
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.
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.
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.
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…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.