Honeycomb. Query datasets, monitor triggers, and investigate incidents from Honeycomb.
Connect your Honeycomb environment to let agents query datasets, check trigger statuses, and investigate production incidents. Agents use your observability data to understand system behavior and identify root causes.
Join the waitlistWhat Polylane does with Honeycomb.
Triggers triaged on arrival
Every Honeycomb trigger that fires lands in Polylane as an issue, and an agent triages it the moment it does, correlated with recent changes across the graph.
Your queries become checks
Every saved query and board becomes a check: agents run it on a cadence and flag what doesn't look like normal for the service behind it.
Queried mid-investigation
Agents query your datasets while they work an incident: high-cardinality questions, answered and cited in the thread.
First-class in the graph
Honeycomb joins the context graph as a source, so a regression in a dataset lands next to the deploy and the resources behind it.
How it works.
Connect
Pick your Honeycomb region and paste a configuration API key. Credentials are encrypted before they're stored.
Sync
Datasets, triggers, and boards join the context graph next to the services that emit the telemetry.
Agents take the watch
Triggers get triaged as they fire, saved queries run as checks, and investigations query Honeycomb directly.
The tools agents get.
What an agent can do with Honeycomb mid-investigation. Every call lands in the thread transcript, cited.
honeycombApi Call any Honeycomb REST endpoint that lacks a dedicated tool
honeycombRunQuery Run a query against a Honeycomb dataset
honeycombDatasets Read Honeycomb datasets and their columns
honeycombTriggers Read or create Honeycomb triggers (alerts)
honeycombBoards Read or create Honeycomb boards (dashboards)
honeycombSLOs Read or create Honeycomb Service Level Objectives (SLOs)
honeycombMarkers List or create markers in a Honeycomb dataset