Question: is there much difference/lacking features of the Serilog.Sentry library (vs main Sentry SDK)?

G’Day 👋🏻 !

With the Sentry.Serilog library, is there much features missing … versus using the main Sentry library?

Context: I prefer to pass ILogger<T> all around my application. In my ConfigureServices, I would prefer to just setup Serilog and then log whatever to wherever, via sinks, like Sentry.Serilog.

So if I get an error, I would then log that to Sentry.

Is it safe to assume that the data which is logged to sentry via the Serilog sink is pretty much feature rich as manually using the Serilog library? Like, rich exception information, etc?

Or in other words, if I use the Sentry.Serilog library, I would be missing out of the following pieces of data:

• <something>
• <another thing>
• etc.

[PureKrome]

Great - created an issue (in preparation for a PR) to test this stuff out, etc.

[bruno-garcia]

Sentry.AspNetCore has appsettngs.json support for default tags. This is missing from Serilog.Sinks.Sentry. A PR to accept this would be considered.

We could move default tags to SentryOptions so all integrations could leverage.

MS Logger supports BeginScope and Sentry (2.1.8+) respects this. So if we use MS Logger + BeginScope + Sentry, we should see the scoped data in Sentry.

It always had it, but before 2.1.8, on ASP.NET Core (with the scope locked) it didn’t keep the values. See #594

Because Sentry respect the MS Logger scopes, by inheritance, the Serilog.Sinks.Sentry nuget library should also handle MS Logger + Scopes.

Serilog does some funny stuff with ASP.NET Core with regards to logging backend. I see the Sink itself adds some Serilog properties stuff as Extra: https://github.com/getsentry/sentry-dotnet/blob/e17703a77a4a5f20b44f233ecfa4e937d42542f8/src/Sentry.Serilog/SentrySink.cs#L109

I suggest trying stuff out though.