The number of crashes on the release page and the discover page differ significantly

[PayneFuRC]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. There are 9.1k crashes in release page
   

2. There are 3.8k crashes in discover page
   

3. There's no dropped crashes

4. There's no filter rules

Expected Result

These two data sets should be the same.

Actual Result

These two data sets differ significantly.

Product Area

Releases

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[PayneFuRC]

And the data from other versions is the opposite, the number of crashes on the release page is lower. If the logic of beforeSend filtered it out, this situation should not exist.

[getsantry]

Routing to @getsentry/product-owners-releases for triage ⏲️

[nhsiehgit]

Hi @PayneFuRC

Thanks for the report!
It looks like our releases page may be deriving this count from somewhere unexpectedly different than our discover page.

I might err on trusting the discover query for the crash rate for now while we dig to understand where this discrepancy is stemming from.

will create an internal ticket for us to track

[nhsiehgit]

Hi @PayneFuRC

Dug into this a bit more
So it looks like the releases page is filtering these events for 'session.status' === 'crashed' as opposed to simply error.unhandled:true

So the releases count actually will be the more proper count!
I'll work with the team to see how we can surface this in a more clear manner.