Skip to content

Python hint about changed grouping by changing of an option #13796

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 22, 2025
Merged

Python hint about changed grouping by changing of an option #13796

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/platforms/python/configuration/options.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,8 @@ When enabled, the SDK will capture a snapshot of local variables to send with th

When capturing errors, Sentry stack traces typically only include frames that start the moment an error occurs. But if the `add_full_stack` option is enabled (set to `True`), all frames from the start of execution will be included in the stack trace sent to Sentry.

Note: Grouping of issues in Sentry is based on stack traces. If you change this value in an existing Sentry setup new groups for already known errors will be created.

</SdkOption>

<SdkOption name="max_stack_frames" type='int' defaultValue='100'>
Expand Down Expand Up @@ -400,7 +402,7 @@ sentry_sdk.init(custom_repr=custom_repr)

<SdkOption name="profile_lifecycle" type='str' defaultValue='manual'>

Determines how the profiler will run, accepts two values: `manual` or `trace`.
Determines how the profiler will run, accepts two values: `manual` or `trace`.

In `manual` mode, you control when the profiler collects data by explicitly calling `sentry_sdk.profiler.start_profiler` and `sentry_sdk.profiler.stop_profiler`. You are entirely in control of when the profiler runs.

Expand Down