-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
docs(flags): update python onboarding docs to include second step #11970
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 1 commit
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 |
---|---|---|
|
@@ -44,3 +44,11 @@ sentry_sdk.capture_exception(Exception("Something went wrong!")) | |
``` | ||
|
||
Visit the Sentry website and confirm that your error event has recorded the feature flag "hello" and its value "false". | ||
|
||
Please read the note below to ensure that you also complete one additional step. | ||
|
||
<Alert level="warning" title="Note"> | ||
|
||
In order to take full advantage of the feature flag capabilities Sentry offers, there is an additional setup step needed, which is setting up your integration-specific webhook. This is needed to enable **feature flag change tracking**, so that your integration may communicate feature flag changes to Sentry. Learn how to set this up by [reading the docs](/product/explore/feature-flags/#set-up-your-integration-specific-webhook). | ||
|
||
</Alert> | ||
|
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.
This sentence might be extraneous
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 agree, I think the note will draw the reader's attention, you probably don't need this callout.