-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
docs(flags): add product index page for feature flags #11969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,40 @@ | ||||||
--- | ||||||
title: "Feature Flags" | ||||||
sidebar_order: 100 | ||||||
description: "Learn how to set up and interact with Sentry's feature flag evaluation tracking and feature flag change tracking." | ||||||
--- | ||||||
|
||||||
<Alert level="info" title="Currently in Beta"> | ||||||
|
||||||
The support for **feature flag change tracking** and **feature flag evaluation tracking** is currently in beta. | ||||||
cmanallen marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
||||||
</Alert> | ||||||
|
||||||
Link your external feature flag integrations with Sentry to provide feature flag insights right inside the Sentry UI. Linking one or more integrations will allow you to view recent flag evaluations in one place and identify potential suspect flags related to errors. In addition, Sentry will provide insights on feature flag updates relative to error event timelines. | ||||||
cmanallen marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
||||||
## Touchpoints | ||||||
|
||||||
Feature flag insights can be found by navigating to the Issue Details page for any error event. There are two places where you can interact with flag data: | ||||||
|
Feature flag insights can be found by navigating to the Issue Details page for any error event. There are two places where you can interact with flag data: | |
Feature flag insights can be found by navigating to the [Issue Details](product/issues/issue-details/) page for any error event. There are two places where you can interact with flag data: |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we write a line or two describing how we determine what's suspect? (broadly speaking)
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, this seems like something we should be saying right here on the product index!
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Setup | |
## Set Up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I notice that's how we write set up on our docs site, so updating for consistency 👁️
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to take advantage of the full feature flag experience available, there are two steps necessary to set up **feature flag evaluation tracking** and **feature flag change tracking**. The first step — setting up the language-specific SDK — is necessary for evaluation tracking, and the second step — setting up your integration-specific webhook — is necessary for change tracking. | |
In order to take advantage of the full feature flag experience, there are two steps necessary to set up **feature flag evaluation tracking** and **feature flag change tracking**. The first step — setting up the language-specific SDK — is necessary for evaluation tracking, and the second step — setting up your integration-specific webhook — is necessary for change tracking. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: should this (and the next title) be sub-titles under ## Setup
? idk
## Set Up Your Language-Specific SDK | |
### Set Up Your Language-Specific SDK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These links both 404, I'm guessing those pages are in development as well; let's make sure we don't merge this until those urls are live.
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to gain access to **feature flag change tracking**, you need to set up a webhook with your specific integration, so that it may communicate feature flag changes with Sentry. | |
In order to gain access to **feature flag change tracking**, you need to set up a webhook with your specific integration, so that it can communicate feature flag changes with Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.