From a7d4c687b35c0007e26ebdb531c1e525fe583a1b Mon Sep 17 00:00:00 2001 From: James Crosswell Date: Thu, 19 Nov 2026 10:37:32 +1300 Subject: [PATCH 1/2] docs(dotnet): Note that the deprecated OpenTelemetry integration doesn't follow ConfigureDataCollection The Sentry.OpenTelemetry span processor won't move onto the DataCollection options (getsentry/sentry-dotnet#5435, closed as not planned). Document what it collects instead and point to the OTLP exporter. Co-Authored-By: Claude Opus 5.5 --- .../common/tracing/instrumentation/opentelemetry.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx index bfb16fdb153ac..c80c32770eee6 100644 --- a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx +++ b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx @@ -30,6 +30,16 @@ OpenTelemetry in .NET is implemented via the System.Diagnostics.Activity namespa Instead you should either log the exceptions (using `ILogger`) or capture the exceptions directly using `SentrySdk.CaptureException`. +## Data Collection + +The user and span attributes this integration collects don't follow `ConfigureDataCollection`. Instead, it: + +- Sets the user from ASP.NET Core only when `SendDefaultPii` is `true`. +- Replaces the values of sensitive URL query parameters on spans, such as `token` or `password`, with `[Filtered]`. +- Sends all other span attributes as they are. + +We recommend migrating to the OTLP exporter. + ## Additional Configuration If you need more fine grained control over Sentry, take a look at the Configuration page. In case you'd like to filter out transactions before sending them to Sentry (to get rid of health checks, for example), you may find the Filtering page helpful. From e970cda8629e754329c887c547c00d4012ced779 Mon Sep 17 00:00:00 2001 From: James Crosswell Date: Thu, 19 Nov 2026 10:51:44 +1300 Subject: [PATCH 2/2] docs(dotnet): Explain ConfigureDataCollection and reword the migration note Co-Authored-By: Claude Opus 5.5 --- .../dotnet/common/tracing/instrumentation/opentelemetry.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx index c80c32770eee6..534b008c0da0d 100644 --- a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx +++ b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx @@ -32,13 +32,13 @@ Instead you should either log the exceptions (using `ILogger`) or capture the ex ## Data Collection -The user and span attributes this integration collects don't follow `ConfigureDataCollection`. Instead, it: +The user and span attributes this integration collects don't follow the options you set with `SentryOptions.ConfigureDataCollection`, an experimental API that controls which data the SDK collects automatically. Instead, it: - Sets the user from ASP.NET Core only when `SendDefaultPii` is `true`. - Replaces the values of sensitive URL query parameters on spans, such as `token` or `password`, with `[Filtered]`. - Sends all other span attributes as they are. -We recommend migrating to the OTLP exporter. +The `Sentry.OpenTelemetry` integration has been deprecated and we recommend migrating to the OTLP exporter to replace this. ## Additional Configuration