getsentry / getsentry/sentry-javascript
[Replays] Ability to exclude specific DOM Elements from Mutation Tracking
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 1.8k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 515
Description
### Problem Statement
The mutation tracking system currently halts replay when significant DOM mutations are detected, with the message:
“Significant mutations detected (N). Replay is now stopped to prevent poor performance for your customer.”
This is helpful for ensuring performance, but it lacks a way to exclude specific DOM elements from mutation tracking (elements that are safe to ignore).
In the customer's case, a specific `
They don't want to increase the mutation limit globally, as that could degrade performance in real problem areas.
and also cannot change or refactor the D3 code for architectural reasons.
### Solution Brainstorm
Add a configuration option or API that allows developers to explicitly exclude certain DOM elements (e.g., via a CSS selector or attribute) from mutation tracking.
### Product Area
Replays
Contributor guide
Assessment
This issue has not been assessed yet.