News for hackers. Stuff that matters.
Re:I gave up on self-hosted Sentry by Weryj on Friday April 18, 2025 @07:12AM (#43726926)
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.

Re:I gave up on self-hosted Sentry by parthdesai on Friday April 18, 2025 @07:54AM (#43727218)
It's open source, you guys could always create a PR to fix it. That's the power of open source!
Re:I gave up on self-hosted Sentry by no_wizard on Friday April 18, 2025 @10:45AM (#43728563)
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.

Re:I gave up on self-hosted Sentry by 5Qn8mNbc2FNCiVV on Saturday April 19, 2025 @01:08PM (#43737725)
It's just a client library, what's the alternative, put a proxy in front that drops 90% of the events
Re:I gave up on self-hosted Sentry by zeeg on Friday April 18, 2025 @02:43PM (#43730778)
Any chance you can link me to the ticket?

Feel free to email - david at sentry

Re:I gave up on self-hosted Sentry by Weryj on Friday April 18, 2025 @05:01PM (#43731832)
It looks like there was some motion a week ago.

https://github.com/getsentry/sentry-dotnet/issues/3636#event...

Re:I gave up on self-hosted Sentry by brungarc on Saturday April 19, 2025 @11:35PM (#43741351)
Avoiding allocations when a transaction isn’t sampled should be pretty trivial. Only gotcha is that you’d still trace id propagation to tie errors together regardless of transactions. But tracing and transactions got decoupled a while ago so shouldn’t be a big problem. I’ll leave a comment on ticket pointing to this post