Allow excluding DOM elements for Sessions Replay mutations

[maximedupre]

Problem Statement

When the mutationLimit is reached:

Sentry Logger [info]: [Replay] Stopping Replay triggered by mutationLimit Sentry Logger [info]: [Replay] Destroying compression worker

One could increase the default mutationLimit but then performances would be degraded

Solution Brainstorm

Allow the exclusion of certain elements, similar to how you can mask or block certain elements with a class or [data-sentry-*] attribute.

This way you could prevent the session replay from being stopped, keep an acceptable mutationLimit, and prevent performance degradation.

[mydea]

Hey, thank you for writing in!

We are unlikely to implement this at this time, because the general mutationLimit is only a rough approximation. If you do not experience issues with a higher number of mutations, you should be fine to raise the limit for your application. Keeping track of what triggers a mutation etc. would just introduce more overhead and decrease performance overall.

[getsantry[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀