Ability to filter by "user-perceived" unhandled exceptions/fatal errors generated by the Kotlin SDK

Problem Statement

Due to the behavior of coroutines exception handling, a failure to catch the exception can sometimes result in a crash, if the request was made from certain contexts, and can be swallowed when made from others.

In both of these cases, Sentry labels the error as level:fatal with exception.handled:false. However, this creates the possibility for a spike in "crashes" that do not actually crash the app for the user.

We recently encountered this issue with a android_getaddrinfo exception, where a user was trying to make a network connection while in airplane mode. What we saw is a huge spike in errors in Sentry, but when we went to Google Play, we were able to filter by user-perceived errors and see that the actual count of crashes for this issue was very very low.

It appears that Sentry's "Crash free user rate" takes into consideration fatal errors that are "user perceived" vs. not (the spike in errors did not impact our crash free user rate).

Solution Brainstorm

We'd love to be able to query by user_perceived:true in Discover, Dashboards, and Alerts (for error data sources) so that we can differentiate between user-perceived vs non-main thread crashes ourselves.

when specifying user_perceived:true, I would expect to only see crashes that resulted in the Android app closing, and contribute to the crash-free user rate shown by Sentry.

when specifying user_perceived:false level:fatal, I would expect to only see errors that are swallowed up by the parent coroutine and do not actually crash the app for the user.

Product Area

Issues

hubertdeng-org / test-sentry-app