From f5690e6c7577147d3ac8f0e85c19d2570b934b98 Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Tue, 14 Oct 2025 15:07:52 -0700 Subject: [PATCH 1/5] Updated dotnet options to include all defaults --- .../dotnet/common/configuration/options.mdx | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index 2e3cd290a051df..b94dce548f2888 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -22,10 +22,10 @@ Learn more about [DSN utilization](/product/sentry-basics/dsn-explainer/#dsn-uti - + - Original - Default .NET stack trace format. -- Enhanced - Include `async`, return type, arguments, and more. +- Enhanced - **default** Include `async`, return type, arguments, and more. Before version 3.0.0 of the Sentry SDK for .NET, there was no special treatment for the stack trace. Sentry reported what .NET made available at runtime. This behavior now called `StackTraceMode.Original`. With the introduction of 3.0, a new default mode is `Enhanced`. @@ -87,7 +87,7 @@ Turns debug mode on or off. If debug is enabled SDK will attempt to print out us - + Enabling `debug` mode makes the SDK generate as much diagnostic data as possible. However, if you'd prefer to lower the verbosity of the Sentry SDK diagnostics logs, configure this option to set the appropriate level: @@ -143,7 +143,7 @@ The maximum number of [envelopes](https://develop.sentry.dev/sdk/data-model/enve - + When enabled, stack traces are automatically attached to all messages logged. Stack traces are always attached to exceptions; however, when this option is set, stack traces are also sent with messages. This option, for instance, means that stack traces appear next to all log messages. @@ -193,11 +193,11 @@ This option can be overridden using . - + This parameter controls whether integrations should capture HTTP request bodies. It can be set to one of the following values: -- `none`: Request bodies are never sent. +- `none`: **default** Request bodies are never sent. - `small`: Only small request bodies will be captured. The cutoff for small depends on the SDK (typically 4KB). - `medium`: Medium and small requests will be captured (typically 10KB). - `always`: The SDK will always capture the request body as long as Sentry can make sense of it. @@ -208,7 +208,7 @@ This parameter controls whether integrations should capture HTTP request bodies. - + Takes a screenshot of the application when an error happens and includes it as an attachment. Learn more about enriching events with screenshots in our Screenshots documentation. @@ -219,7 +219,7 @@ Learn more about enriching events with screenshots in our - + The quality of the attached screenshot. It can be set to `full`, `high`, `medium` or `low`. @@ -227,13 +227,13 @@ The quality of the attached screenshot. It can be set to `full`, `high`, `medium - + Set this boolean to `false` to disable sending of client reports. Client reports are a protocol feature that let clients send status reports about themselves to Sentry. They are currently mainly used to emit outcomes for events that were never sent. - + Once enabled, this feature automatically captures HTTP client errors, like bad response codes, as error events and reports them to Sentry. @@ -328,15 +328,15 @@ The default is `1` (one) second. - + -Controls how many seconds to wait before shutting down. Sentry SDKs send events from a background queue. This queue is given a certain amount to drain pending events. The default is SDK specific but typically around two seconds. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems. +Controls how many seconds to wait before shutting down. Sentry SDKs send events from a background queue. This queue is given a certain amount to drain pending events. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems. ## Tracing Options - + A number between `0` and `1`, controlling the percentage chance a given transaction will be sent to Sentry. (`0` represents 0% while `1` represents 100%.) Applies equally to all transactions created in the app. Either this or must be defined to enable tracing. From 4689ca8b9eccb7217519d762fc601060db740abd Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Tue, 14 Oct 2025 15:35:09 -0700 Subject: [PATCH 2/5] changing the shutdowntimeout langauge --- docs/platforms/dotnet/common/configuration/options.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index b94dce548f2888..cbe0a41aaefeec 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -328,9 +328,9 @@ The default is `1` (one) second. - + -Controls how many seconds to wait before shutting down. Sentry SDKs send events from a background queue. This queue is given a certain amount to drain pending events. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems. +Controls how many seconds to wait before shutting down. Sentry SDKs send events from a background queue. This queue is given a certain amount to drain pending events. The default is SDK specific but typically around two seconds. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems. From 9b6cda56b122984a2a0dfdcb517260351be21d7c Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Wed, 22 Oct 2025 09:48:10 -0700 Subject: [PATCH 3/5] Update docs/platforms/dotnet/common/configuration/options.mdx Co-authored-by: Stefan Jandl --- docs/platforms/dotnet/common/configuration/options.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index cbe0a41aaefeec..4f577921a9a32e 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -233,7 +233,7 @@ Set this boolean to `false` to disable sending of client reports. Client reports - + Once enabled, this feature automatically captures HTTP client errors, like bad response codes, as error events and reports them to Sentry. From 19f9c175bc826f024d928477be74735a23b313cd Mon Sep 17 00:00:00 2001 From: bitsandfoxes Date: Thu, 23 Oct 2025 10:21:02 +0200 Subject: [PATCH 4/5] Removed 'ScreenshotQuality' --- docs/platforms/dotnet/common/configuration/options.mdx | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index 4f577921a9a32e..cafde77e268d25 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -217,16 +217,6 @@ Learn more about enriching events with screenshots in our - - - -The quality of the attached screenshot. It can be set to `full`, `high`, `medium` or `low`. - - - - - Set this boolean to `false` to disable sending of client reports. Client reports are a protocol feature that let clients send status reports about themselves to Sentry. They are currently mainly used to emit outcomes for events that were never sent. From 0dbcd72956577cb7ab7fad21ea64bb001fecde6a Mon Sep 17 00:00:00 2001 From: Alex Sohn <44201357+alexsohn1126@users.noreply.github.com> Date: Thu, 23 Oct 2025 10:53:13 -0400 Subject: [PATCH 5/5] Capitalize Enhanced for StackTraceMode --- docs/platforms/dotnet/common/configuration/options.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index cafde77e268d25..c4c6c06096e3eb 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -22,7 +22,7 @@ Learn more about [DSN utilization](/product/sentry-basics/dsn-explainer/#dsn-uti - + - Original - Default .NET stack trace format. - Enhanced - **default** Include `async`, return type, arguments, and more.