You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Replays] Ability to exclude specific DOM Elements from Mutation Tracking #16831
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 <div> generates frequent mutations due to an SVG visualization library (D3.js). These mutations are expected and not relevant to user interaction tracking. However, they contribute heavily to the mutation count, triggering the above warning and halting replay.
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.
@dalnoki actually, I think it can be excluded if it is blocked
Hello, I'm the one behind the request. I tried to add the id of the svg to the block list and alternatively with data-sentry-block, tried to increase the range of blocked div, but still have this problem.
That's why I created a ticket. I just tested back now and experienced the same problem.
Activity
getsantry commentedon Mar 27, 2025
Assigning to @getsentry/support for routing ⏲️
getsantry commentedon Mar 27, 2025
Routing to @getsentry/product-owners-replays for triage ⏲️
billyvg commentedon Mar 27, 2025
This feature request makes sense to me, we'll talk about it and discuss prioritization.
billyvg commentedon Apr 23, 2025
@dalnoki actually, I think it can be excluded if it is blocked
SteamWind commentedon May 26, 2025
Hello, I'm the one behind the request. I tried to add the id of the svg to the block list and alternatively with
data-sentry-block, tried to increase the range of blocked div, but still have this problem.That's why I created a ticket. I just tested back now and experienced the same problem.
13 remaining items
SteamWind commentedon Jul 14, 2025
Thanks, is it still in experiment?
andreiborza commentedon Jul 14, 2025
@SteamWind yes, but you should be able to use it safely.
feat(rrweb): Allow onMutation to return a filtered list of mutations (#…