ENGINEERING
Critical-path slow trace → Sentry correlation → PagerDuty escalation
When a trace on a critical service exceeds a tight latency budget and correlates with a spike in Sentry errors, this workflow opens a PagerDuty incident and attaches the joined…
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb slow-trace alert on critical serviceHoneycomb
- LogicVerify critical-path allowlist + tight budget overage
- ActionQuery Sentry and gate on error-rate spikeSentry
- ActionCreate GitLab issue with joined evidenceGitLab
- OutputOpen linked PagerDuty incident, route to policyPagerDuty
What it does
Distinguishes a real outage from a slow page. For traces on protected critical-path services, it checks Honeycomb latency against a tight budget, confirms a correlated Sentry error surge, and — only then — escalates to PagerDuty while filing a linked GitLab issue so responders have evidence the moment they're paged.
When to use it
Use for your most important services where slow + erroring means customer impact. Best when you want paging reserved for correlated signals, not raw latency, to cut alert fatigue while protecting SLOs.
How it works
- 1A Honeycomb trigger fires on a slow trace tagged to a critical service.
- 2The workflow verifies the service is on the critical-path allowlist and the overage clears the tight budget.
- 3It queries Sentry and gates on whether error rate spiked above baseline in the window.
- 4If both conditions hold, it creates a GitLab issue with the joined trace and error context.
- 5It opens a PagerDuty incident referencing the issue and routes to the owning escalation policy.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect SentryErrors, performance, releases.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect GitLabRepos, MRs, pipelines, registry.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.