ENGINEERING
Sustained Budget Breach to PagerDuty
On a schedule, scan Honeycomb for query shapes that have stayed over their latency budget for a sustained period and open a PagerDuty incident with the worst offender and its…
How it runs
The automated pipeline, trigger to output.
- Trigger15-minute schedule
- ActionFetch p95 for governed query shapesHoneycomb
- LogicKeep sustained over-budget breaches
- LogicMap offender to owning service
- OutputOpen PagerDuty incidentPagerDuty
What it does
Not every slow query traces back to a single PR. This workflow continuously checks every governed query shape against its budget, and when one stays over the envelope long enough to count as a real problem rather than a blip, it opens a PagerDuty incident routed to the owning service with the query, duration, and trend.
When to use it
Use it for the queries that matter most to availability, where a sustained latency breach should page someone rather than wait for the next code review. Pair it with the per-shape ownership map.
How it works
- 1A schedule triggers the scan every 15 minutes.
- 2A Honeycomb action fetches current p95 for all governed query shapes.
- 3A logic step keeps only shapes over budget and confirms the breach has persisted across consecutive intervals.
- 4A logic step maps the worst sustained offender to its owning service and severity.
- 5A PagerDuty action opens or updates an incident with the query, the breach duration, and a Honeycomb trace link.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.