From 2cf0a26b3cbdaecb16d7b87ff1df9ebd54ef924f Mon Sep 17 00:00:00 2001 From: James Crosswell Date: Mon, 7 Jul 2025 15:42:32 +1200 Subject: [PATCH 1/2] Clarify behaviour for AggregateExceptions in the SetBeforeSend hook Resolves https://github.com/getsentry/sentry-dotnet/issues/3751 --- docs/platforms/dotnet/common/configuration/options.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index e30acddd48e99..d0ba9d1eca462 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -225,6 +225,8 @@ This function is called with an SDK-specific message or error event object, and By the time is executed, all scope data has already been applied to the event. Further modification of the scope won't have any effect. +If filtering based on exception types, the original exception (including any `AggregateException`) will be stored in `SentryEvent.Exception`. However Sentry's `MainEventProcessor` unpacks AggregateExceptions automatically and so what you will see in the Sentry UI will be the various inner exceptions. These are also available in the SDK by inspecting the `SentryEvent.SentryExceptions` collection. + From 9f6de5012cc26d89cc0d5b06f9b69480f8075cb9 Mon Sep 17 00:00:00 2001 From: James Crosswell Date: Wed, 9 Jul 2025 09:36:40 +1200 Subject: [PATCH 2/2] Update docs/platforms/dotnet/common/configuration/options.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Stefan Pölz <38893694+Flash0ver@users.noreply.github.com> --- 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 d0ba9d1eca462..fe0f6529b27ee 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -225,7 +225,7 @@ This function is called with an SDK-specific message or error event object, and By the time is executed, all scope data has already been applied to the event. Further modification of the scope won't have any effect. -If filtering based on exception types, the original exception (including any `AggregateException`) will be stored in `SentryEvent.Exception`. However Sentry's `MainEventProcessor` unpacks AggregateExceptions automatically and so what you will see in the Sentry UI will be the various inner exceptions. These are also available in the SDK by inspecting the `SentryEvent.SentryExceptions` collection. +When filtering based on exception types, the original exception (including any `AggregateException`) will be stored in `SentryEvent.Exception`. However, Sentry's `MainExceptionProcessor` unpacks AggregateExceptions automatically, and so what you will see in Sentry will be the various inner exceptions. These are also available in the SDK by inspecting the `SentryEvent.SentryExceptions` collection.