Open
Description
Context
When processing a Replay we have DOM and other relevant data that can help us detect some errors.
This issue tracks ideas of Replay Issues we can create.
Detection Ideas
- "Too many DOM Nodes" Replay Issue #76852
- [Epic] Hydration Errors #70199
- Related to the NextJS effort, hydration errors are currently filtered out by most orgs because they are not actionable (the only debugging context that we get comes from a
console.error()message) - With replay we can see the before/after state of the page when that hydration error happened, thus make the error actionable by zooming in on the content that changed.
- https://www.notion.so/sentry/Make-hydration-errors-more-actionable-8e12a96d68ab4316a332681a821374a6
- https://www.notion.so/sentry/Hydration-Errors-in-Replays-b50365c658374c179d719bf2de9e2a43
- Related to the NextJS effort, hydration errors are currently filtered out by most orgs because they are not actionable (the only debugging context that we get comes from a
- Blank screen of death
- Detect when certain frameworks render their generic error page (ie: nextjs has a default 500 error page)
- More generic detection of blank pages: ie
<body>has no nodes inside it (ignoring , <script> etc). - @ryan953 live demoing this case at DEX, recording on YouTube
- Rage click
- N clicks in <M ms, the user seems frusterated, possibly at not getting feedback or is unsure of the click is registered.
- [Epic] Capture events for Dead Clicks #48259
- Error click
- Clicking a button that is consistently the most recent breadcrumb before an issue/error
- Infinite spinner - invalid page navigation flow
- CSS/Spinner, get redirected back, infinite redirects
- Accessibility issues
- Poor color contrast?
- Missing aria attrs on clickable elements?
- Detecting too many repaints
- Excessive Mutations
- Memory Usage cc/ @JoshFerge
- Repetitive error: same error multiple times in a row, coming from a loop or something
- Use Replay data to advise users how to optimize
<head>element #67146 - https://github.com/getsentry/team-replay/issues/76
- Detect when a link is broken and leads to a 404 or some other 'bad' page