> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlog.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Honeycomb

> Connect Honeycomb with a management key so Superlog can read your events and traces, and start automations from triggers and SLO burn alerts.

Superlog reads your Honeycomb events and traces through Honeycomb's MCP server.

## Connect Honeycomb

**1. Create a management key**

In Honeycomb, open **Team Settings → API Keys → Management Keys** and create a key. Only team owners can. Give it read access to **Model Context Protocol** and **Environments**.

**2. Connect**

In Superlog, open **Integrations** and click **Add** on Honeycomb. Choose the **Region**, **US** or **EU**, paste the **Key ID** and **Key secret**, and click **Connect Honeycomb**.

## How findings use Honeycomb

* **Sweeps.** If none of your telemetry reaches Superlog, Superlog checks Honeycomb every 15 minutes for new problems. See [How findings work](https://docs.superlog.sh/findings/how-it-works.md#where-problems-come-from).
* **Investigations.** Superlog queries Honeycomb for evidence and impact while it investigates any problem.

## Start automations from Honeycomb

**1. Add the trigger**

In the automation editor, click **Add trigger** and choose **Honeycomb → Trigger or SLO alert**. Click **Set up Honeycomb webhook**.

**2. Add the webhook**

In Honeycomb, open **Team Settings → Integrations** and add a **Webhook**. Use the webhook URL and shared secret from Superlog, and keep the default payload.

**3. Add it as a recipient**

Add the webhook as a recipient on the triggers and burn alerts that should start the automation. Each alert starts a run.

## Access

What Superlog can do is limited to the scopes on your key. Investigations use only read-only tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.