Stefan Pölz

Metrics are currently in beta, and we are continuously widening the support for our SDKs. And our .NET SDK is indeed on the Roadmap: we plan to ship Metrics as...

Sorry @intrepid-developer ... I might have jumped the gun here a bit, considering all the other things we have on our plate ... in particular #4427, as well as rounding...

Thank you so much, @ericsampson!

@ericsampson, please reach out to me via Email ([email protected]) or any other channel listed in my profile (@Flash0ver) ... we want to say "thank you" for your high-quality contributions with...

See also: #4720

> Isn't that what `System.Threading.Channels` is designed for? It's pretty highly optimized, and has optional flags for SingleProducer and SingleConsumer to further optimize perf for those conditions. https://devblogs.microsoft.com/dotnet/an-introduction-to-system-threading-channels/ For intra-process-producer/consumer-scenarios,...

We are thinking about removing `SentryOptions.EnableScopeSync` from the public API surface area, and instead have it implicitly enabled by user code setting a `SentryOptions.ScopeObserver`, or our Native/Android/iOS implementations setting a...

Discussed again: We keep all options, but will add wrappers/combiners/aggregators for both `CrashedLastRun` and `ScopeObserver`, so that user-provided instances/delegates will not overwrite the ones that we set.

I like that, as it reminds me of [RS2008](https://github.com/dotnet/roslyn/blob/main/src/RoslynAnalyzers/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md).

Thank you, @KaliCZ, for using our new integration so quickly, and for the detailed report. At first glance, this could be related to initializing 2 `Hub`s, a bit of a...