Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Honeycomb connector page.What StackOne provisions automatically
When you connect a Honeycomb account, StackOne creates a team-level webhook recipient named StackOne via the Honeycomb API, pointing at your connection’s callback URL and carrying a shared secret. Honeycomb echoes that secret back in the X-Honeycomb-Webhook-Token header on every delivery. You do not need to create or copy any URL yourself. Removing the connection deletes the recipient — but Honeycomb refuses to delete a recipient that any Trigger or Burn Alert still references, so remove the StackOne recipient from those alerts first, otherwise the disconnect reports a conflict and the recipient is left in place.
Attach the StackOne recipient to your alerts
Honeycomb only posts to a recipient that an alert explicitly references, and there is no API to attach a recipient to every alert at once. Repeat these steps for each Trigger, SLO Burn Alert and Anomaly Detection you want delivered to StackOne.
Attach to a Trigger
Open the Trigger you want events from.
- Go to your environment and open Triggers
- Select the trigger, then click Edit
- Under Recipients, click Add Recipient
- Choose Webhook, then select the StackOne recipient
- Click Save
Attach to an SLO Burn Alert
Burn alerts are configured on the SLO that owns them.
- Go to your environment and open SLOs
- Select the SLO, then open its Burn Alerts
- Edit an existing burn alert or create one
- Under Recipients, add the StackOne webhook recipient
- Click Save
Attach to Anomaly Detection
Anomaly Detection notifications are configured per monitored signal.
- Open Anomaly Detection in your environment
- Select the signal you want notifications for
- Add the StackOne webhook recipient to its notification settings
- Save the configuration.