Expand set of maskable fields in RUM
See original GitHub issueIs there any chance we could add more fields to the list mentioned in the docs, which we can mask or redact in beforeSend
?
Also is there any chance we can expose the fields that we can’t edit even if as readonly
?
Last question: is there any way in which we can mask or hide data related to the location/device of the user?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Session Replay Privacy Options - Datadog Docs
By enabling Session Replay, you can automatically mask sensitive elements from being recorded through the RUM Browser SDK.
Read more >Configure environment-wide data privacy settings - Dynatrace
Learn how to set up data privacy masking for end user IP addresses, ... From the Dynatrace menu, go to Settings > Preferences...
Read more >Getting started with measuring Web Vitals - web.dev
Real User Monitoring (RUM) data, also known as field data, captures the performance experienced by a site's actual users. RUM data is what ......
Read more >RUMlog 5.0 - The User's Manual - dl2rum.de
Mode Field and Mode Popup (5) ... RUMlog can interface with your transceivers, setting the main parameter on ... F - Spread sheet...
Read more >The Differences Between Rums | A Beginners Guide
The different types of rum available, their countries of origin and which brands ... which 151 overproof rums should be used for setting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For now, there is no way to easily configure that through the SDK or the Datadog application but it is an interesting use case. You could maybe use a proxy setup to control if the original ip should be forwarded or not.
For this example,
view.url_path_group
is processed on the backend side so you need to send aview.url
and for now there is no option to hideview.url
afterwards.However, you could parse
view.url
yourself inbeforeSend
and sanitize all the parts that you don’t want to expose and keep the path in order to let the backend process the path group.Something like:
Would it work for you?