ENGINEERING
Slow trace + Sentry error → deploy-blame note on the GitLab merge request
Correlates a budget-breaching Honeycomb trace with concurrent Sentry errors, finds the most recent GitLab deploy/merge that touched the affected service.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb over-budget trace alert (webhook)Honeycomb
- ActionPull correlated Sentry errors for the windowSentry
- ActionFind most recent GitLab MR touching the serviceGitLab
- LogicBranch: culprit MR found vs fall back to new issue
- OutputComment joined evidence on the merge requestGitLab
What it does
Points latency regressions back at the change that likely caused them. When a slow trace correlates with Sentry errors, the workflow identifies the most recent merge to the affected service and comments the trace + error evidence directly on that GitLab merge request, so the author sees the regression in the context of their own change.
When to use it
Use when most latency regressions trace back to a recent deploy and you want feedback to land where the author already looks. Ideal for teams practicing continuous deployment who want fast attribution without a separate triage ticket.
How it works
- 1A Honeycomb trigger fires on a trace exceeding its latency budget.
- 2The workflow pulls correlated Sentry errors for the service and window.
- 3It queries GitLab for the most recent merged MR touching that service before the trace timestamp.
- 4It branches: if a likely-culprit MR is found, build a blame note; otherwise fall back to a new issue.
- 5It posts the joined trace and error evidence as a comment on the suspect merge request.
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.