From dacf3a86a54908b89fc6bb154f12211d607a2831 Mon Sep 17 00:00:00 2001 From: Anton Pirker Date: Sat, 16 Nov 2024 15:20:39 +0100 Subject: [PATCH 1/2] Added new options to control what frames to add to the stack trace --- docs/platforms/python/configuration/options.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/platforms/python/configuration/options.mdx b/docs/platforms/python/configuration/options.mdx index b52e6dda1f47f2..13ed8e75716f32 100644 --- a/docs/platforms/python/configuration/options.mdx +++ b/docs/platforms/python/configuration/options.mdx @@ -131,6 +131,22 @@ This option is on by default. + + +When capturing errors, the Sentry stack traces only contain the frames from when an error happens. If this option is enabled (set to `True`) all frames from the beginning of the execution will be added to the stack trace sent to Sentry. + +Default value is `False`. + + + + + +This option limits the number of stack frames that will be captured. Limiting is only applied if `add_full_stack` is enabled. + +Default value is `100`. + + + 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. From 24bb7381a8efa936aa33bf9bf9c86d10b58b7369 Mon Sep 17 00:00:00 2001 From: Anton Pirker Date: Fri, 6 Dec 2024 16:49:54 +0100 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Liza Mock --- docs/platforms/python/configuration/options.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/platforms/python/configuration/options.mdx b/docs/platforms/python/configuration/options.mdx index 13ed8e75716f32..b106beff185cc9 100644 --- a/docs/platforms/python/configuration/options.mdx +++ b/docs/platforms/python/configuration/options.mdx @@ -133,17 +133,13 @@ This option is on by default. -When capturing errors, the Sentry stack traces only contain the frames from when an error happens. If this option is enabled (set to `True`) all frames from the beginning of the execution will be added to the stack trace sent to Sentry. - -Default value is `False`. +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`. -This option limits the number of stack frames that will be captured. Limiting is only applied if `add_full_stack` is enabled. - -Default value is `100`. +This option limits the number of stack frames that will be captured when `add_full_stack` is enabled. The default value is `100`.