Show total match count on Replays list page
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
The Replays list page (and its underlying API) has no way to see a total count of replays matching the current search, including combined filters like count_errors:>0 release:X. Users can only page through results with cursor-based pagination and count manually.
organization_replay_index.pyuses a cursor-basedReplayPaginator(Linkheader next/prev only); the response never includes a total count field.- The frontend (
replayIndexContainer.tsx) only reads theLinkheader for prev/next state, so there's nothing to surface even if a user wanted it. - There is also no Dashboards
WidgetTypefor replays (views/dashboards/types.tsxonly covers discover/issue/metrics/errors/transactions/spans/logs/tracemetrics/preprod-app-size), so acount()aggregate widget over replays isn't possible either.
This makes it hard to answer questions like "how many error-linked replays happened on release X" without manually paging through the list.
Request: add a total match count (or a count() aggregate path via Discover/Dashboards) for the Replays list/search, similar to how Issues search shows counts.
Requested by kpujji via Junior.
--
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 with organization_replay_index.py and its cursor-based ReplayPaginator to understand the current response and pagination headers. Then read replayIndexContainer.tsx and views/dashboards/types.tsx to trace frontend handling and existing widget types. Done means filtered Replays searches expose a total match count through the API and make it available in the list or an agreed Discover/Dashboards path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- api, backend-api-design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100