feat(replays): Track event and video event counts on replay load#114001
Merged
feat(replays): Track event and video event counts on replay load#114001
Conversation
Emit a Sentry metric distribution once per replay load, after all segments have been fetched, recording the number of video segments the player received with the project_id as an attribute. This gives us visibility into the segment-count distribution for mobile replays in the wild, which is otherwise only answerable via aggregated Snuba queries against `replays_aggregated`. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Extract replayId, projectId, videoElementCount as locals so the useEffect can list all its dependencies explicitly. Drop the eslint-disable and the now-redundant comment. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Extract the metric emission into a useEffectEvent so the useEffect only needs to depend on replayId and isFetching — the latest videoElementCount, projectId, and isVideoReplay are read at call time. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Match the JavaScript convention for metric names. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
nsdeschenes
approved these changes
Apr 27, 2026
JoshuaKGoldberg
approved these changes
Apr 27, 2026
3 tasks
cleptric
pushed a commit
that referenced
this pull request
May 5, 2026
…4001) Add some Replay telemetry to count the number of segments, especially video segments. Having too many videos (>1,000) seems like it's causing Chrome crashes, and I'd like to both know how often that happens, and be able to find exemplars. This is in support of REPLAY-831 --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add some Replay telemetry to count the number of segments, especially video segments. Having too many videos (>1,000) seems like it's causing Chrome crashes, and I'd like to both know how often that happens, and be able to find exemplars. This is in support of REPLAY-831