AI AGENTS
Honeycomb weekly latency-regression leaderboard
On a weekly schedule, an agent ranks the endpoints whose latency degraded most week-over-week in Honeycomb, writes a digest with likely causes.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly latency-leaderboard schedule fires
- ActionQuery per-endpoint latency this week vs. lastHoneycomb
- ActionRank endpoints by week-over-week regressionHoneycomb
- LogicSplit top offenders from the rest
- OutputPost ranked digest to SlackSlack
- ActionOpen GitLab issues for worst endpointsGitLab
What it does
Gives engineering leadership a weekly view of where latency is quietly getting worse. The agent compares this week's per-endpoint latency to last week's in Honeycomb, ranks the biggest regressions, and produces a digest — posted to Slack for visibility and turned into GitLab issues for the top offenders.
When to use it
When slow creep matters as much as acute alerts and you want a regular, prioritized list of what to fix. Ideal for performance reviews, sprint planning, or a weekly reliability ritual.
How it works
- 1A weekly schedule triggers the digest run.
- 2The agent queries Honeycomb for per-endpoint latency this week and the prior week.
- 3It ranks endpoints by week-over-week regression to build a leaderboard.
- 4A branch separates the top offenders worth issues from the rest of the list.
- 5The agent drafts a digest with each regression's likely cause and posts it to Slack.
- 6It opens GitLab issues for the worst endpoints so they enter the backlog.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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 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.