Since I want to get every single exception logged, Sentry feels quite useless and I wouldn't select it for my next project.
Other than that it has been a fantastic tool.
Since I want to get every single exception logged, Sentry feels quite useless and I wouldn't select it for my next project.
Other than that it has been a fantastic tool.
That's very different than if e.g. you're a payments provider, and you literally need to know every transaction that erred, but that's also quite a different use case. In my opinion, you'd want to guarantee those errors are logged elsewhere (traditional audit logs), and utilize Sentry primarily for the workflow and alerting features.
Ideally speaking a Sentry exception is the last escape hatch - if we can't handle something in code at least the error is sent somewhere so that developers can handle the issue. Following this the philosophy I'd like to follow is that every time I get a Sentry exception, I'll make a new ticket in Jira "handle error x, see link to Sentry", and ultimately there wouldn't be any errors sent to Sentry.