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

…11844) Documentation of two new options that where introduced here: getsentry/sentry-python#3673 --------- Co-authored-by: Liza Mock <[email protected]>
getsentry · Dec 6, 2024 · 217b4d3 · 217b4d3
1 parent 310124b
commit 217b4d3
Showing 1 changed file with 12 additions and 0 deletions.
diff --git a/docs/platforms/python/configuration/options.mdx b/docs/platforms/python/configuration/options.mdx
@@ -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.