Session Replay: Track SDK options

[jas-kas]

Session Replay SDK offers a number of different privacy configurations and other options.

We'd like to see in...

• How many times each option is being used (enabled on the client)
• How often our default privacy configuration is being changed from masking all text and media

This can help drive product decisions, and assist in debugging (assuming we can see SDK options at an org level)

[billyvg]

We'll likely want to add it to context similar to #6659 (and only on first segment).

[Lms24]

I think this is a worthwhile change and as long as we're collecting that a certain option was used and not how (e.g. masking selectors), we don't need to worry about sensitive data.

We'll likely want to add it to context similar to #6659 (and only on first segment).

Agreed

[billyvg]

@Lms24 Are the selectors considered sensitive data? We would likely have that data already when we record their DOM. Having their customization would mean that we can debug if their selectors are incorrect.

[Lms24]

My concern is that free text generally can include all kinds of input which we can't control and I didn't want to risk PII ending up in places we're not aware of. Also, we decided to be super cautious about collecting options in our bundler plugins, where we also only collect minimal information about options that can potentially contain any kind of data.

Furthermore, reading the issue description, I thought this was what we wanted to do anyway.

[mydea]

There is some ongoing effort to generally capture SDK configuration on Sentry.init. IMHO we should use the same mechanism to also capture replay SDK config.

My current WIP idea is to capture:

• Config + values for all config that is boolean or numbers
• Only existence of config option for string options

So e.g. something like:

{ 
 config: {
 replay: { 
 maskAllText: false,
 mask: 'DEFINED' // or some other thing to indicate this was set
 }
}

[bruno-garcia]

Sounds like this was shut down. We need to collect a summary on why this can't go forward.

Additionally, we need to rethink this ticket and write down what problems we need to solve that we hoped this feature would give us. For example: How often users don't use the default masking options:

• How often our default privacy configuration is being changed from masking all text and media

[jas-kas]

@mydea to add more information :)

[mydea]

So the heartbeat in this form is not going to happen for now, as there are concerns about storage/frequency of data being sent etc.

We'll continue thinking about a way to solve this in a generic way, but for now it's better to think about this separately for replay-specific use cases!