ENGINEERING
Live p95 outlier pager with bisect-to-commit escalation
When Honeycomb fires a p95-breach trigger, correlates the spike to the most recent deploy, opens a PagerDuty incident only if the regression survives a confirmation re-check.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb p95-breach triggerHoneycomb
- ActionRe-query Honeycomb to confirm sustained regressionHoneycomb
- LogicIf cleared exit; else correlate onset to deploy timeline
- ActionLook up suspect commit from GitLab deploy timelineGitLab
- OutputOpen PagerDuty incident with suspect commit and linkPagerDuty
What it does
This workflow listens for a Honeycomb trigger that fires when a query's p95 crosses an alerting threshold in real time. Rather than paging on the first blip, it re-queries Honeycomb a short time later to confirm the regression is sustained, then correlates the spike's onset timestamp against the GitLab deploy timeline to identify the release that most likely introduced it. If confirmed, it opens a PagerDuty incident annotated with the suspect commit and a deep link to the Honeycomb view.
When to use it
Reach for this when a slow-query regression is severe enough to warrant a real page, not just a ticket — checkout, auth, or any latency-critical path. The confirmation re-check suppresses transient noise so on-call only wakes for sustained regressions.
How it works
- 1Honeycomb p95-breach trigger fires.
- 2Re-query Honeycomb after a delay to confirm the regression is sustained.
- 3If it cleared, exit; otherwise correlate onset time to the GitLab deploy timeline for the suspect commit.
- 4Open a PagerDuty incident with the suspect commit and Honeycomb link.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.