diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index 2e3cd290a051d..c4c6c06096e3e 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. @@ -217,23 +217,13 @@ 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. - + Once enabled, this feature automatically captures HTTP client errors, like bad response codes, as error events and reports them to Sentry. @@ -336,7 +326,7 @@ Controls how many seconds to wait before shutting down. Sentry SDKs send events ## 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.