Installation
Establish Authentication
To set up Honeycomb, you will need to first log into Honeycomb as an admin user. Once logged in, make sure you are on the environment that you’re looking to integrate with Rootly and select the settings icon ⚙️.
Honeycomb has two types of API keys: Configuration and Management API keys.The one Rootly requires is a Configuration (aka. Environment-level) API key.

Name
and check any of the permissions. Once complete, go ahead and save the API key.
Integrating with an API key is purely to authenticate Rootly as a client to your Honeycomb environment, so we can generate a webhook URL + secret combination that is exclusive to your organization. Rootly will NOT be making any direct calls to Honeycomb to read or write. Rootly will only be ingesting incoming alerts from Honeycomb.The Honeycomb integration will be moved to Rootly Alert Sources, so this step will eventually be obsolete.

To get to the Honeycomb integration modal, you’ll need to be an Admin user in Rootly and navigate to Integrations > Honeycomb > Setup


Create a Webhook
Now that you have your organization specific webhook URL + secret combination, let’s go to your Honeycomb account to create a webhook. Once logged in, navigate to the Team settings page.

Provider
to Webhook
and give it a description Name
(e.g. Page Engineering On-Call, Page Infrastructure Team, Rootly Alerts, etc.).

Webhook URL
field will depend on what type of alert you want this particular webhook to send to Rootly.
For General Alert (aka. Non-Paging Alert)
Non-paging alerts will arrive in Rootly’s Alerts page but will not page anyone.
Honeycomb requires the Webhook URL and secret from Rootly to be included in the Webhook URL field in the following format:
Webhook URL
The webhook URL and secret can be obtained from your Honeycomb integration page in Rootly (Integrations > Honeycomb > Configure).

Yes, the secret need to exist both as part of the
Webhook URL
path AND in the Shared Secret
field. Make sure that the secret in both places are exactly the same.resource_type
- this defines the Rootly resource type that will be used for paging.- The following are the available values:
User
|Group
(Team) |EscalationPolicy
|Service
- The following are the available values:
resource_id
- this specifies the exact resource that will be targeted for the page.- The id of the resource can be found when editing each resource.
Webhook URL
field in Honeycomb:
Webhook URL

Yes, the secret need to exist both as part of the Webhook URL path AND in the Shared Secret field. Make sure that the secret in both places are exactly the same.
Uninstall
You can uninstall this integration in the integrations panel by clicking Configure > Delete.