For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Integrations
    • Collaboration tools
    • Data Export
    • Edge tools
    • Environments as a service
    • Experimentation and metric integrations
    • Internal developer platforms
    • Monitoring tools
      • AppDynamics
      • AWS CloudWatch RUM
      • Chronosphere
      • Datadog
      • Dynatrace
      • Elastic (ELK) Stack
      • Grafana
      • Honeycomb
        • Using the Honeycomb events integration
        • Using flag triggers with Honeycomb
      • Last9
      • Mezmo
      • New Relic One
      • PagerDuty for guarded rollouts
      • Splunk
      • Splunk Observability Cloud (formerly SignalFx)
    • Segments integrations
    • Workflow management tools
    • More integrations
    • Managing integrations
    • Using the LaunchDarkly integration framework
    • Building partner integrations
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Prerequisites
  • Create a Honeycomb API key
  • Add the Honeycomb integration
  • Configure integration policies
IntegrationsMonitoring toolsHoneycomb

Using the Honeycomb events integration

Was this page helpful?
Previous

Using flag triggers with Honeycomb

Next
Built with
The Honeycomb events integration is available to customers on select plans

The Honeycomb events integration is only available to customers on select plans. To learn more, read about our pricing. To upgrade your plan, contact Sales.

Overview

This topic explains how to use the LaunchDarkly Honeycomb events integration.

The LaunchDarkly Honeycomb integration helps you diagnose problems by sending flag events to Honeycomb. Honeycomb displays those events alongside performance graphs so you can correlate feature rollouts with changes in operational health.

A Honeycomb events graph showing LaunchDarkly flag change events, with a flag event called out.

A Honeycomb events graph showing LaunchDarkly flag change events, with a flag event called out.
The integration only sends flag actions to Honeycomb

Only flag action events appear in Honeycomb after you configure the integration. Other event kinds do not appear. To learn more, read Feature flag actions.

To send flag change events to Honeycomb:

  1. Create a Honeycomb API key.
  2. Add the Honeycomb integration in LaunchDarkly.
  3. (Optional) Configure the integration’s policy to allow or restrict specific projects and environments.

Prerequisites

To use the LaunchDarkly Honeycomb integration successfully, you must meet the following prerequisites:

  • You must have an API key from your Honeycomb account. To learn more, read Create a Honeycomb API key.

Create a Honeycomb API key

The Honeycomb API key authenticates the LaunchDarkly integration so it can submit events to your Honeycomb account. The LaunchDarkly integration uses Honeycomb’s Marker API.

To learn more about Honeycomb’s Marker API, read Honeycomb’s documentation.

When you create the API key, confirm that the key has access to create “markers.” This is the only access scope the LaunchDarkly integration needs.

Add the Honeycomb integration

Here’s how to add the Honeycomb integration:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Integrations and find “Honeycomb.”
  3. Click Add integration. The “Create Honeycomb configuration” panel appears.
  4. (Optional) Type a human-readable Name.
  5. Enter the Honeycomb dataset name you would like flag markers to be associated with.
  6. Paste in your Honeycomb API key.
  7. (Optional) Configure a custom policy to control which flag information LaunchDarkly sends to Honeycomb. To learn more, read Configure integration policies.
  8. After reading the Integration Terms and Conditions, check the I have read and agree to the Integration Terms and Conditions checkbox.
  9. Click Save configuration.

Configure integration policies

The “Edit policy” field in the integration configuration panel lets you control which events LaunchDarkly sends to Honeycomb.

The default policy allows production environments across all projects to send events. To update the policy, use the policy builder or by click View JSON and edit the policy statements directly.

Here’s the resources specifier from the default policy:

Production environments across all projects
proj/*:env/production:flag/*

To learn more, read Using resources.

You can use the policy editor to restrict the integration to:

  • a specific set of LaunchDarkly projects/environments
  • a specific set of flags
  • a specific set of actions

For example, to restrict the policy to a single project called cool-app, set the policy configuration’s resources field to the following resource specifier:

Restrict to a single project
proj/cool-app:env/production:flag/*

The policy above makes the integration only send flag events from the cool-app project’s Production environment to Honeycomb.

If you need to restrict or allow a more complex set of resources than you can specify in a single policy, you can add multiple Honeycomb integrations and configure each one to a specific task. Each integration can have its own separate policy configuration.

To learn more about using the policy editor, read Using policies.