SentrySdk.CaptureException should add a breadcrumb for future exceptions

[emrys90]

Problem Statement

It appears that when you call SentrySdk.CaptureException, it does not add a breadrcrumb of itself, which means the next SentrySdk.CaptureException call does not show the previous exception in the dashboard. This seems like critical information to have by default, as its quite common for one exception to trigger another if things aren't handled well, and you will lose that contextual awareness that this exception was caused by a different exception happening.

Solution Brainstorm

No response

[bitsandfoxes]

Ha, that's a super valid point! I never realized the SDK not doing that! Coming from the Unity SDK I just expected it to be there. The only instances I found where the Core SDK would add breadcrumbs itself were the BeforeSend and BeforeSendTransaction callbacks to let users know that it blew up: https://github.com/getsentry/sentry-dotnet/blob/5e54f086b1269f8251a9a388b1de38ee10779cb4/src/Sentry/SentryClient.cs#L208-L212 https://github.com/getsentry/sentry-dotnet/blob/5e54f086b1269f8251a9a388b1de38ee10779cb4/src/Sentry/SentryClient.cs#L443-L447

@bruno-garcia @jamescrosswell any thoughts on this? I can see this being an opt-in feature?

[bruno-garcia]

We do this on the logging libraries. It makes sense to me, I think it was an oversight.

But take into account that we'd be double writing in the logging integrations, so we'd need to remove those.

https://github.com/getsentry/sentry-dotnet/blob/a11f10399e2e2258c211557cb7a9a6b4af84f94c/src/Sentry.Serilog/SentrySink.cs#L119

Would need a refactor. Or if we don't want to change the current behavior on the logging libraries, we could skip this new breadcrumb if the event was written by one of our logging libraries (by for example checkign against the sdk name)

[ericsampson]

Either of the suggestions that bruno made sound good. Especially if it doesn't require/cause any user-facing changes (ie have the logging libraries do the right thing automatically)

[bitsandfoxes]

That would not even require being added in the next mayor.

[jamescrosswell]

I think it's cleanest to do it once/always when capturing an exception and make sure the logging libraries either capture an exception or drop a breadcrumb (not both).