> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/honeycomb.md). # Honeycomb Integration The ilert Honeycomb Integration helps you to easily connect ilert with Honeycomb. [Honeycomb](https://www.honeycomb.io/) is a tool for observability, designed to help developers understand and debug their software systems by providing real-time insights and detailed, queryable data about production environments. ## In ilert: Create a Honeycomb alert source 1. Go to **Alerting** → **Alert sources** and click **Create new alert source**. 2. Search for **Honeycomb**, click its tile, and click **Next**. 3. Give your alert source a name, optionally assign teams, and click **Next**. 4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below.

Pick an existing escalation policy, or generate a basic one without leaving the wizard.

5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving. 6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later. 7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide. ## In Honeycomb: Create a Webhook Trigger 1. On the sidebar click on **Account -> Team settings**.
2. On the next page click on **Integrations**.
3. Now scroll down and click on **Add Integration**.
4. In the popup window: Change the **Provider** to Webhook and choose a desired **Name**. Now insert the ilert Honeycomb URL and api key from [the previous created alert source](#in-ilert-create-a-honeycomb-alert-source) into **Webhook URL** and **Shared Secret**. 5. Click on **Add** to save the integration.
6. Optionally: On the Trigger and SLO Recipients section, click on **Test**, to send a test webhook to ilert.
7. Now on the sidebar, click on **Triggers**.
8. Select a desired trigger template. (This documentation uses Latency)
9. Select a dataset and click on **Next**.
10. After configuring the trigger, scroll down to the **Recipients** section and click on **Add Recipient**.
11. Select the previously created webhook as **Recipient** and click on **Add**. 12. Save the trigger.
13. Optionally: In the triggers list click on the **Test** button to send a test webhook to ilert.
## FAQ **Will alerts in ilert be resolved automatically?** Yes, as soon as Honeycomb sends a notification with 'OK' status, corresponding alerts in ilert will be resolved automatically. --- # 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://docs.ilert.com/integrations/inbound-integrations/honeycomb.md?ask=&goal= ``` `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.