ENGINEERING
Nightly latency-budget sweep: batch slow traces into one GitLab epic
Runs every night to query Honeycomb for all traces that breached their latency budget that day, correlates each with Sentry errors.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly scheduled sweep
- ActionQuery Honeycomb for all over-budget traces (24h)Honeycomb
- ActionFetch Sentry error counts per service windowSentry
- LogicRank by duration overage + error volume, keep top N
- OutputWrite ranked daily GitLab digest issueGitLab
What it does
Replaces a flood of per-trace alerts with one daily digest. A scheduled sweep pulls the day's budget-breaching Honeycomb traces, correlates each with Sentry errors, ranks them by impact, and writes a single GitLab issue listing the top offenders with links and suggested owners — ready for standup.
When to use it
Use when real-time paging is overkill but you still want latency regressions tracked. Great for teams that review reliability once a day and want a prioritized, deduplicated list rather than scattered notifications.
How it works
- 1A scheduled trigger runs nightly after traffic settles.
- 2The workflow queries Honeycomb for all traces over budget in the past 24 hours.
- 3For each distinct service it fetches the day's Sentry error counts in the matching windows.
- 4It ranks traces by a blend of duration overage and correlated error volume, keeping the top N.
- 5A single GitLab issue is created (or updated for the day) with the ranked table and per-row trace and error links.
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
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.