Update list of default In-App stack traces excludes

[tvardero]

Description

Consider adding following entries to SentryOptions.GetDefaultInAppExclude:

• MySqlConnector - MySQL database connector
• Pomelo.EntityFrameworkCore.MySql - EF provider for MySQL
• Yarp - "Yet Another Reverse Proxy" by Microsoft
• Rebus - RabbitMQ handler (MassTransit alternative)
• Amazon - Amazon S3, Secrets Manager, etc.
• ZiggyCreatures.FusionCache - Caching framework, HybridCache implementation
• OpenTelemetry - OpenTelemetry
• EntityFramework.Exceptions.Common - DbUpdateException rewriter
• object InvokeStub_TaskAwaiter - Hangfire wrapper for scheduled/enqueued async jobs
• TickerQ - Hangfire alternative
• Duende.IdentityModel - OAuth client credentials flow helper
• Duende.AccessTokenManagement - OAuth client credentials flow helper
• Xero - Xero accounting software

Also there are lots of other nugets that are really popular across .NET community, however I can't say what their correct namespace is:

• Mediator (source-generated MediatR alternative)
• Quatrz (Hangfire alternative)
• Masstransit
• Microsoft Azure stuff (in case if they dont start with Microsoft.)
• EntityFramework providers for MS SQL, SQLite, Postgres, etc.
• Quickbooks (Xero alternative)
• others?

sentry-dotnet/src/Sentry/SentryOptions.cs

Line 1864 in 18bfa9e

internal static List<StringOrRegex> GetDefaultInAppExclude() =>

[linear]

NET-558

[Flash0ver]

Thanks for opening this issue, @tvardero, and sharing your additional thoughts.

Do I assume correctly that the first list are libraries that you actually use in your application(s)?
Can you try / confirm whether adding these to your project via SentryOptions.AddInAppExclude does indeed mark the respective Stack Frames as "in_app = false"?

Thought: I wonder if there is a more "generic"/"stable" solution to solve this problem instead of maintaining a list of exclusions of varying popularity within the ecosystem to match against Module/Package/Function 🤔 because this "general" list here is essentially pessimizing (perf) all consumers that don't use most of this collection ... e.g. by assembling the lookup at run-time on startup via Reflection, or at build-time through Source-Generation.

[tvardero]

Can you try / confirm whether adding these to your project via SentryOptions.AddInAppExclude does indeed mark the respective Stack Frames as "in_app = false"?

Yes, we already do for those, they work correctly. For the second list - I don't have those libraries in my project, so I don't know what their correct namespace is.

About generic solution - no idea. Preferebly all Nuget packages, but I don't know any marker to use to distinct nuget assemblies from my project assemblies.
One solution might be marking all my assemblies with some interface/marker/source-generated assembly attribute/etc., so Sentry might know which assemblies are actual user code. But them what if author of Nuget packages uses same trick and those marker leak into nuget assemblies?

UPD: Another solution is to explicitly tell Sentry what stack traces are "In-App". Any non-listed namespaces are treated as non-in-app.