ENGINEERING
Weekly slow-query regression digest to Notion
Every week, aggregates all p95 regressions Honeycomb saw, groups them by the deploy that introduced each, ranks by user-facing impact.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull all weekly p95 regressions from HoneycombHoneycomb
- ActionPull week's release log from GitLabGitLab
- LogicRank by impact and group regressions by deploy
- OutputPublish formatted digest page in NotionNotion
What it does
On a weekly cadence, this workflow queries Honeycomb for every query whose p95 regressed during the week, attributes each regression to the deploy window it appeared in, and joins that against the GitLab release log to name the introducing release. It ranks regressions by impact — p95 delta multiplied by request volume — and publishes a structured Notion page: a summary table up top, then per-deploy sections with the affected queries and deltas. It gives engineering leadership a single artifact to review in the weekly performance review.
When to use it
Use this when you want a rollup rather than per-incident noise — a recurring document that makes latency trends and the deploys responsible visible to the whole team, including people who do not watch Honeycomb daily.
How it works
- 1Weekly schedule trigger fires.
- 2Pull all p95 regressions for the week from Honeycomb.
- 3Pull the week's release log from GitLab to map regressions to deploys.
- 4Rank by impact (p95 delta times volume) and group by deploy.
- 5Publish the formatted digest as a Notion page.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect NotionPages, databases, comments.
- 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.