But if I need another tool for logging those errors, I could use the same tool for both use cases, which would make Sentry unnecessary? Ideally speaking a Sent

But if I need another tool for logging those errors, I could use the same tool for both use cases, which would make Sentry unnecessary? 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.