Skip to content

Commit d49e1c1

Browse files
Clarify behaviour for AggregateExceptions in the SetBeforeSend hook (#14265)
1 parent 1113a79 commit d49e1c1

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/platforms/dotnet/common/configuration/options.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -225,6 +225,8 @@ This function is called with an SDK-specific message or error event object, and
225225

226226
By the time <PlatformIdentifier name="set-before-send" /> is executed, all scope data has already been applied to the event. Further modification of the scope won't have any effect.
227227

228+
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.
229+
228230
</ConfigKey>
229231

230232
<ConfigKey name="set-before-breadcrumb">

0 commit comments

Comments
 (0)