Skip to content

Commit 920a532

Browse files
committed
Merge branch 'cmanallen/add-issue-details-docs' of https://github.com/getsentry/sentry-docs into cmanallen/add-issue-details-docs
2 parents f00a3fa + 22d9ec4 commit 920a532

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,13 @@ If you’ve enabled [Session Replay](/product/explore/session-replay/), you’ll
103103
![Session Replay](./img/issue-replay.png)
104104

105105
## Feature Flags
106-
If you’ve enabled a feature flag integration in your SDK you’ll have access to the feature flag table. If any flags were captured after the Sentry SDK's initialization and before the error event occurred, the table will contain rows of flag, evaluation-result pairs.
106+
There are two types of integrations you can configure to integrate feature flag data into your error events.
107+
108+
The first is to configure runtime feature flag evaluation tracking in the sentry SDK. Doing this will give you access to the feature flag table which shows any flags that were evaluated after the Sentry SDK's initialization and before the error event occurred. You will see rows of flag, evaluation-result pairs.
109+
110+
The second is to configure feature flag change tracking. This will enable a timeline of feature flag changes inside the releases graph. These annotations can help you diagnose when a feature flag change is related to a new issue.
111+
112+
When both of these integration are enabled you will also see suspect feature flags highlighted inside the feature flag table. Feature flags are suspect when their modification occurs suspiciously close to the initial detection of a new issue. Suspect feature flags are displayed are given a yellow highlight within the feature flag table.
107113

108114
![Feature Flags](./img/feature-flags.png)
109115

0 commit comments

Comments
 (0)