ENGINEERING
Slow Honeycomb trace → Sentry error correlation → GitLab issue
When a Honeycomb trace blows past its latency budget, this workflow pulls the concurrent Sentry errors for the same service and time window and files a single enriched GitLab…
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb latency-budget trigger fires (webhook)Honeycomb
- LogicConfirm trace exceeds budget and has a service name
- ActionQuery Sentry for concurrent errors on that serviceSentry
- LogicJoin slow span breakdown with matching error fingerprints
- OutputCreate enriched GitLab issue with trace + error contextGitLab
What it does
Turns a latency alarm into an actionable, pre-investigated ticket. A slow trace detected in Honeycomb is automatically cross-referenced with the Sentry errors that fired during the same span, and the combined evidence — slow trace ID, span breakdown, and matching exceptions — lands in one GitLab issue so an engineer starts from a hypothesis instead of a blank page.
When to use it
Use when p95/p99 latency spikes are common but tedious to triage, and you suspect they correlate with backend errors. Ideal for teams that already alert on Honeycomb triggers but waste time manually jumping to Sentry to find the related failures.
How it works
- 1A Honeycomb trigger fires when a trace exceeds the configured latency budget and posts the trace metadata via webhook.
- 2The workflow checks whether the trace duration clears the budget threshold and has a resolvable service name.
- 3It queries Sentry for unresolved errors on that service within the trace's start/end window.
- 4If matching errors exist, it joins the slow span breakdown with the top Sentry issues into one context block.
- 5A GitLab issue is created with the trace link, error fingerprints, and a suggested owner label.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect SentryErrors, performance, releases.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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.