Skip to content

Commit b0bbf64

Browse files
committed
Add more docs
1 parent 1cf3e8e commit b0bbf64

File tree

4 files changed

+19
-4
lines changed

4 files changed

+19
-4
lines changed
48.3 KB
Loading

docs/organization/integrations/feature-flag/launchdarkly/index.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ sidebar_order: 1
44
description: Learn about Sentry's LaunchDarkly integration. LaunchDarkly enables organizations to use Sentry errors as a metric in their LaunchDarkly experiments.
55
---
66

7+
## Metrics Integration
8+
79
This integration is maintained and supported by the company that created it. For more details or questions, feel free to contact [email protected].
810

911
## Install and Configure
@@ -23,3 +25,9 @@ The LaunchDarkly integration is only available to organizations with a Business
2325
1. Navigate to **Settings > Integrations > LaunchDarkly**
2426

2527
2. Follow the full [LaunchDarkly installation instructions](https://docs.launchdarkly.com/integrations/sentry).
28+
29+
## Change Tracking Integration
30+
31+
Sentry offers a flag change tracking integration which allows Sentry to associate flag definition changes with errors that occurred in your application. To enable this integration, create a new <Link to="https://app.launchdarkly.com/settings/integrations?q=generic+trigger">"Generic Trigger"</Link> integration and paste the Sentry web hook URL generated by the Feature Flag Integration Modal. For information on how to generate a Sentry Web Hook URL visit the <PlatformLink to="/product/issues/issue-details/#feature-flags">feature flag integration documentation here</PlatformLink>. Learn more about LaunchDarkly's "Generic Triggers" <Link to="https://docs.launchdarkly.com/home/releases/triggers">here</Link>.
32+
33+
![LaunchDarkly Integration UI](./img/launchdarkly-ui.png)
145 KB
Loading

docs/product/issues/issue-details/index.mdx

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -107,16 +107,23 @@ If you’ve enabled a feature flag integration in your SDK you’ll have access
107107

108108
![Feature Flags](./img/feature-flags.png)
109109

110-
A timeline of suspect flags is also available if you've enabled at least one flag-audit-log integration.
111-
112-
!TODO! To enable a flag audit log click this button for the popup. Afterwards copy paste your web hook URL into the service provider. !TODO!
110+
A timeline of feature flag changes is displayed in the releases graph. These annotations can help you diagnose when a feature flag change is responsible for a new bug report.
113111

114112
![Feature Flags](./img/suspect-flags-timeline.png)
115113

116-
Suspect flags are displayed in the table with a yellow highlight.
114+
Additionally, feature flag definition changes can be flagged as suspect when their modification occurs suspiciously close to the creation of an error event. Suspect feature flags are displayed are given a yellow highlight within the feature flag table.
117115

118116
![Feature Flags](./img/suspect-flags-table.png)
119117

118+
To enable suspect feature flags and feature flag change annotations, click the "Set Up Integration" button on the feature flag table and follow the instructions. Provider specific instructions are provided by clicking the "Read Docs" button.
119+
120+
![Feature Flags](./img/feature-flag-modal.png)
121+
122+
To learn more about enabling the Change Tracking integration, visit the documentation for one of the supported providers below.
123+
124+
* [LaunchDarkly](/organization/integrations/feature-flag/launchdarkly/)
125+
126+
120127
## Breadcrumbs
121128

122129
![Breadcrumbs](./img/issue-breadcrumbs.png)

0 commit comments

Comments
 (0)