# Honeycomb

EvoHub receives Honeycomb trigger notifications through a **webhook integration**. Honeycomb's default payload is read as it is: a trigger that fires opens an EvoHub alert, and the same trigger returning to OK resolves it.

## Set it up

:::steps
### Create the integration
In EvoHub, go to **On-Call → Integrations → + Add Integration**, choose **Honeycomb**, pick an **Escalation Policy** and click **Create Integration**. Copy the **Webhook URL**.
### Create the webhook
In Honeycomb, go to **Team settings → Integrations → Add integration → Webhook**. Set **Webhook URL** to your webhook URL and leave **Secret** empty — the key in the URL authenticates the call. If you prefer the key out of the URL, remove `?key=…` from it and paste the key as the **Secret** instead.
### Test it
Click **Test**. EvoHub answers with success and opens no alert.
### Add it to triggers
In each trigger, add the webhook under **Recipients**.
:::

## What EvoHub reads

| EvoHub alert | Taken from |
| --- | --- |
| Title | The trigger `name`. |
| Description | `description`, followed by the trigger's own description. |
| Severity | **high**. |
| Labels | `trigger_id`, `operator`, `threshold`, `trigger_url`, `groups` (the groups that crossed the threshold) and `url` (the query result). |

## Resolve and deduplication

An alert is identified by the trigger. Repeat firings while it is open are recorded as **Retriggered**; `status` `OK` resolves it.

## Related

- [Integrations overview](https://docs-dev.evohub.io/integrations-overview.md)
- [AppDynamics](https://docs-dev.evohub.io/appdynamics.md)