AI AGENTS
Honeycomb latency-regression investigator to GitLab
When a Honeycomb p95 latency trigger fires, an agent pivots the traces to find the slowest span and culprit service.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb p95 latency threshold breachedHoneycomb
- ActionPull slowest exemplar traces in alert windowHoneycomb
- ActionPivot spans by service and operation durationHoneycomb
- LogicBranch: single dominant span vs. distributed latency
- ActionAgent drafts ranked regression hypothesis
- OutputOpen GitLab issue with hypothesis and trace linkGitLab
What it does
Turns a Honeycomb latency alert into a fully-formed engineering investigation. The agent doesn't just forward the alert — it pivots the offending traces, isolates the slowest span and the service responsible, and writes a GitLab issue stating its best hypothesis for the regression.
When to use it
When your p95 or p99 latency SLO breaches and you want a head start on triage instead of a raw alert that someone has to investigate from scratch. Ideal for teams who live in Honeycomb for observability and GitLab for engineering work.
How it works
- 1A Honeycomb trigger fires when a service's p95 latency crosses its threshold.
- 2The agent queries Honeycomb to pull the slowest exemplar traces in the alert window.
- 3It pivots the spans by service, operation, and duration to find where time is actually spent.
- 4A branch checks whether one span dominates the latency or it's spread across many.
- 5The agent drafts a ranked hypothesis (e.g., "DB call in checkout-svc regressed 4x after deploy abc123").
- 6It opens a GitLab issue with the hypothesis, the affected service, and a deep-link back to the trace.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.