Skip to main content
Customize Honeycomb alerts with variables for precise, actionable notifications.

Introduction

Use variables to customize payloads for your Honeycomb trigger alerts and SLO burn alerts. These variables dynamically populate your webhook payloads, ensuring that alerts contain the relevant information for your workflows. To learn more about working with variables in custom webhooks, visit Custom Webhooks: Define Payload Template Variables and Custom Webhooks: Override Payload Template Variables.

Simple Example

You can reference a variable in a JSON payload template like this:
In this example, .Alert.Summary is a variable that dynamically evaluates to the summary of the alert when the webhook is sent.

Array Variables

When using variables that return arrays, wrap them with toJson to generate valid JSON:
In this example, the .Datasets variable contains a list of dataset names associated with the alert. Wrapping the variable with toJSON ensures proper JSON formatting.
Omitting toJson for array variables will trigger an error like: Failed to send: invalid character 'e' in literal true (expecting 'r').

Variables for Triggers

Trigger variables provide contextual information about alerts. Use them to customize payloads for your integrations.

Variables for SLO Budget Rate Burn Alerts

These variables provide information about SLO burn alerts for monitoring error budget consumption.

Variables for SLO Exhaustion Time Burn Alerts

Use these variables when configuring burn alerts that monitor projected SLO exhaustion time.