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.
The Grafana integration is available to customers on select plans
The Grafana 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 Grafana integration. You can use the integration to send flag, environment, and project updates to Grafana as annotations to add context to your graphs.
An example Grafana dashboard configured with LaunchDarkly feature flag change event annotations.
Prerequisites
To use the Grafana integration, you must have the following prerequisites:
A Grafana instance that is accessible to LaunchDarkly’s servers.
A Grafana service account with the “Annotation writer” role and a corresponding service account token.
Create a Grafana service account and service account token
After you create a service account token in Grafana, you can set up the integration in LaunchDarkly.
Click the gear icon in the left sidenav to view Organization settings.
Click Integrations and find “Grafana.”
Click Add integration. The “Create Grafana configuration” panel appears.
(Optional) Give your integration a human-readable Name.
Enter your Grafana instance URL. Do not include a trailing /.
Enter the Grafana service account token. You created this token in the Prerequisites section.
(Optional) Configure a custom policy to control which events LaunchDarkly sends to Grafana. To learn more, read Filter the events you send to Grafana.
After reading the Integration Terms and Conditions, check the I have read and agree to the Integration Terms and Conditions checkbox.
Click Save configuration. The new integration appears on the Integrations page. It is switched On by default.
After you set up the Grafana integration, events from LaunchDarkly appear in your Grafana dashboard.
Filter the events you send to Grafana
By default, LaunchDarkly sends events to Grafana for changes made to any feature flag, environment, or project. If you have a more limited use case for using the integration, or you wish to restrict which data you send to Grafana, you can filter which events LaunchDarkly sends.
To filter events, write a policy using the same syntax as the role policy builder to filter the events sent to Grafana.
For more information about writing policies, read Using policies.
For example, if you only want to receive an event when a change is made to one of the feature flags in your testing environment, you can add the following policy to your events stream:
Navigate to the Integrations page and find “Grafana.”
Click the overflow menu next to the configuration you wish to modify, and select “Edit integration configuration.” The “Edit Grafana configuration” panel appears.
The configuration overflow menu with the "Edit integration configuration" option called out.
In the “Policy” section, click Advanced editor. The Advanced editor appears.
Enter your custom policy.
Click Save configuration.
You can verify that LaunchDarkly is sending a customized set of events by viewing the events in your Grafana dashboard.
Add LaunchDarkly annotations to Grafana dashboards
To add LaunchDarkly events as annotations in Grafana dashboards:
Open the Grafana dashboard in edit mode.
Click the Dashboard settings gear icon button located at the top of the page.
Click Annotations.
Click New query. The “New annotation” page appears.
Enter a human readable name for the annotation, such as “LaunchDarkly feature flags.”
In the Data source menu, select ”— Grafana —.”
In the Filter by menu, select Tags.
The Grafana "Add annotation" page.
The LaunchDarkly integration sends annotation events to Grafana with event-specific tags. You can use one or more of the following tags to filter the annotations that appear on your dashboard:
Tag
Description
launchdarkly
This tag is added to all LaunchDarkly annotation events.
ld_tag:TAG
The LaunchDarkly tag associated with the resource that changed. For example, if a feature flag has the tag
grafana in LaunchDarky, all event annotations associated with that flag will be sent to Grafana with the tag
ld_tag:grafana.
project_key:PROJECT_KEY
The LaunchDarkly project key that is associated with the change event.
environment_key:ENVIRONMENT_KEY
The LaunchDarkly environment key that is associated with the change event.
flag_key:FLAG_KEY
The LaunchDarkly feature flag key that is associated with the change event. This tag is only applied to feature
flag change events.
segment_key:SEGMENT_KEY
The LaunchDarkly segment flag key that is associated with the change event. This tag is only applied to segment
change events.
kind:RESOURCE_KIND
The resource kind associated with the change event where RESOURCE_KIND is one of flag, segment, project,
environment, or member.