AI AGENTS
Honeycomb + Axiom cross-source latency root-cause
On a Honeycomb latency trigger, an agent cross-references the trace window against Axiom application logs to confirm the failing dependency.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb latency trigger firesHoneycomb
- ActionPull slowest spans and time windowHoneycomb
- ActionQuery Axiom logs for same service and windowAxiom
- LogicConfirm log evidence supports trace suspect
- ActionSynthesize root-cause from both sources
- OutputFile GitLab issue with correlated evidenceGitLab
What it does
Combines distributed traces with raw logs to produce a higher-confidence root cause. When latency regresses in Honeycomb, the agent pulls the matching log lines from Axiom for the same time window and service, correlates them, and files a GitLab issue backed by evidence from both observability sources.
When to use it
When traces alone tell you where time is spent but not why, and the answer (timeouts, retries, error spikes) lives in your logs. Ideal for teams running Honeycomb for tracing and Axiom for log analytics.
How it works
- 1A Honeycomb latency trigger fires for a service.
- 2The agent pulls the slowest spans and their time window from Honeycomb.
- 3It queries Axiom logs for the same service and window, filtering for errors, retries, and timeouts.
- 4A branch confirms whether log evidence supports the trace-level suspect.
- 5The agent synthesizes a root-cause statement citing both the trace and the log lines.
- 6It opens a GitLab issue with the correlated evidence and links to each source.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect AxiomLog streams, queries, dashboards.
- 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.