I do have one major complaint though, in dotnet, the tracing/errors are always captured regardless of the sampling rate. So you end up with a lot more memory usage on high throughput/low memory services with no way to lower it.
There's a ticket now open to stop this, but it's still in progress.
It's open source, you guys could always create a PR to fix it. That's the power of open source!
there's no guarantee it will get merged though, even if a PR is created.
Forking has down sides that can't be hand waved away too, especially for a service like this.
It's just a client library, what's the alternative, put a proxy in front that drops 90% of the events
Any chance you can link me to the ticket?
Feel free to email - david at sentry
It looks like there was some motion a week ago.
https://github.com/getsentry/sentry-dotnet/issues/3636#event...