Skip to content

Added new options to control what frames to add to the stack trace #11844

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

Merged
merged 2 commits into from
Dec 6, 2024
Merged
Changes from all commits
Commits
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
12 changes: 12 additions & 0 deletions docs/platforms/python/configuration/options.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,18 @@ This option is on by default.

</ConfigKey>

<ConfigKey name="add-full-stack">

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. By default, this option is set to `False`.

</ConfigKey>

<ConfigKey name="max-stack-frames">

This option limits the number of stack frames that will be captured when `add_full_stack` is enabled. The default value is `100`.

</ConfigKey>

<ConfigKey name="server-name">

This option can be used to supply a "server name." When provided, the name of the server is sent along and persisted in the event. For many integrations, the server name actually corresponds to the device hostname, even in situations where the machine is not actually a server.
Expand Down
Loading