Changing the exception title in Sentry?

[davidames]

This is similar to #270 in that the title of the Sentry exception in the dashboard will often be an aggregate exception or a DbUpdateException - with the really useful information in the inner exception.

I've been "playing" with how to resolve this. Ideally, we would preserve all the exceptions as they contain stack traces with different information.

The closest that I've come is to have an BeforeSend which generates a new SentryEvent based on the incoming SentryEvent and returning that but doing

SentryExceptions = sourceEvent.SentryExceptions.Reverse()

This achieves my goal of getting the inner exception title on the dashboard -is there another way as this kind of feels clunky.

[bruno-garcia]

It's a good point that having AggregateException isn't very helpful.
If you don't mind, please upvote #270 and let's close this as a duplicate.

In case you'd like to try a PR on this, it would be helpful although I don't think just reversing the exceptions is the way to go. Often the top most exception is what you want to see. It's the case of AggregateException and maybe a handful others that they are just wrappers.

Perhaps a list of Exception types to drop altogether. There's a code snippet on #270 on how to drop a single type, we could just extend that to be more generic.

Also, note you don't need to return a new instance of the event. You can just modify it.