getsentry / getsentry/sentry-javascript

[Replays] Ability to exclude specific DOM Elements from Mutation Tracking

Offen
#16,831 11 Kommentare 2 Reaktionen 1 zugewiesene Person Beansprucht von @billyvg Auf GitHub ansehen
Explore > Replays Feature Replays
Vorherrschende Sprache
TypeScript
Sterne
8.7k
Forks
1.8k
Ø Merge
1 T. 17 Std.
Gemergte PRs (30 T.)
515

Beschreibung

### 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 `

` 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.

### Product Area

Replays

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.