Honeycomb

Honeycomb context enriches an existing Pulse. It does not create Pulses.

How this helps triage: matching excerpts can show up in the summary, the first checks, and What informed this on the Pulse.

Exhale uses a Honeycomb API key at triage time to attach team and trace/query excerpts.

This is not trigger webhook ingest. If Honeycomb triggers should become Pulses, connect Sources → Honeycomb.

Connect

1. Sign in as a workspace admin.
2. Open Connections → Context → Observability context → Honeycomb.
3. Save the API key, then Test connection.
4. Test connection to mark the connector configured.

See Honeycomb's official guide: Manage Environment API Keys.

Missing credentials, timeouts, or vendor 403s skip this block. Triage still completes. Send-test-alert Pulses skip live collectors.

Plan

Growth or higher.

Connector slots are shared across Context categories (markdown runbooks use a separate document cap). Tighten AI → Prompt → Context use if excerpts are noisy or too large.

API

Writes use the signed-in session and CSRF. Secrets are never returned on GET.

Related trace lines and deep links attach when the key has the needed scopes.

Related

• Context index
• Prompt → Context use