ENGINEERING
Nightly p99 query regression digest tied to the day's deploys
Each night this compares today's slowest queries in Honeycomb against yesterday's baseline and posts a Slack digest that pairs each regression with the deploys most likely…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionPull per-query p99 and baseline from HoneycombHoneycomb
- LogicFlag queries that regressed past the margin
- ActionMatch GitHub deploys to each regression windowGitHub
- OutputPost ranked regression digest to SlackSlack
What it does
Produces a once-a-day scorecard of which database queries got slower and which deploys probably caused it. It diffs today's per-query p99 against the prior baseline and attaches the deploys that shipped during each query's regression.
When to use it
Use it when you want a steady morning pulse on query health rather than only reacting to alerts — catching the slow creep that never trips a single-threshold trigger but compounds over a week.
How it works
- 1A scheduled run fires every night after the deploy freeze.
- 2It queries Honeycomb for per-query p99 over the last 24 hours and the prior 7-day baseline.
- 3A logic step flags queries whose p99 rose beyond the regression margin.
- 4For each flagged query it pulls the GitHub deploys that landed during the rise.
- 5It assembles a ranked digest pairing each regression with its candidate deploys.
- 6The digest posts to the engineering Slack channel with trace and commit links.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.