> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/honeycomb.md).

# Honeycomb

[<mark style="color:blue;">Honeycomb</mark>](https://www.honeycomb.io/) is an application monitoring tool that helps DevOps and SRE teams to operate more efficiently by offering rich observability and intuitive team collaboration.

Route detailed alerts from Honeycomb to the right users in Squadcast.

### Using Honeycomb as an Alert Source

1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.

![](/files/ej4AI9zpOyFu5NZJCbwC)

2\. Select **Honeycomb**. Copy the displayed **Webhook URL** to [configure](#create-a-squadcast-webhook-trigger-in-honeycomb) it within **Honeycomb.** Finish by clicking **Add Alert Source** -> **Done**.

![](/files/TzocHaTEhFqjFIL0vtSN)

{% hint style="warning" %}
**Important:**

When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
{% endhint %}

### Create a Squadcast Webhook Trigger in Honeycomb

**(1)** Login to your Honeycomb dashboard. Head over to the **Account** settings and click on **Team settings**

![](/files/NQU41b8ZoJWFWayKeoip)

**(2)** Under the **Integrations** section, click on **Add Integration**

![](/files/Xb62VX3KxXWM1pb3FeK1)

**(3)** Choose **Webhook** as **Provider**, fill in the **Name**. Paste the previously copied Squadcast Webhook URL in the placeholder for **Webhook URL**. Fill in the **Shared Secret**, then click on **Add**

![](/files/OW7R7moFCyZldSYTkww9)

**(4)** Under the **Triggers** tab, click on **New Trigger**. Choose the dataset of your choice and click on **Make Trigger**

![](/files/p5xQWIu6ao9ZFpED2VX8)

![](/files/67Ygquo2MzH74kOOOLj6)

**(5)** Under the **Triggers** section, set the **Name** and **Description** of the trigger. Choose the **State** as **Enabled**. Set the query, frequency and duration for the trigger. Then click on **Add Recipient**

![](/files/Xwn1o6RqUME3w28aeAZg)

![](/files/OmN4XmKO3EZw62gspXYl)

**(5)** Choose the **Integration** created earlier as **Recipient** and click on **Add**. Finally, click on **Create Trigger**

![](/files/bZ7lamQZKj7hQP8QZ0yo)

![](/files/PSs8VTDI288if5BPpnIX)

That's it, you are good to go! Your Honeycomb integration is now complete. Whenever Honeycomb fires an alert, an incident will be created in Squadcast for it. Also, when an alert is resolved in Honeycomb, the corresponding incident gets **auto-resolved** in Squadcast.

*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/honeycomb.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
