ANR Rate scorecard and chart show non-comparable values
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
On the Android project details page, the ANR Rate scorecard (top row) and the ANR Rate chart display values that can appear contradictory — e.g. a scorecard of 0.81% while the chart's highest daily point is only 0.27% for the same date range.
Both widgets query the same anr_rate() derived metric (anr_user_count / all_user_count, unique users), but at different granularities: the scorecard aggregates unique users across the full selected period (includeSeries: false), while the chart computes the ratio per daily bucket (getSessionsInterval with dailyInterval: true). Because "unique user" counts don't dedupe consistently across different window sizes, the ratios aren't averageable across buckets — the period-aggregate value can legitimately exceed the highest single-day bucket value. This is not a computation bug, but it produces a confusing, seemingly-contradictory pair of numbers on the same page.
Proposed UX improvements (not yet validated against design/product priorities):
- Add scope-qualifying labels/tooltips distinguishing "period aggregate" vs. "daily" ANR rate (e.g. scorecard help text vs. chart axis/legend copy).
- Show the period-aggregate value as a reference line/annotation on the chart so the two numbers are visually connected.
- Consider a toggle for chart bucket size (daily/weekly/cumulative) so it can visually converge toward the scorecard aggregate.
Related prior issue on the same category of problem (aggregate vs. time-bucketed rate mismatch): #58396.
via Michael Chai.
--
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Android project details page and inspect the ANR Rate scorecard and chart, including their shared anr_rate() metric and differing aggregation paths. Review related issue #58396 and validate the proposed UX direction with design or product; done means the period aggregate and daily values are clearly distinguished and no longer appear contradictory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- analytics, data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100