Dynatrace offers environment-wide settings that serve to ensure your compliance with the data-privacy regulations of your region.
Mask end users' IP addresses and GPS coordinates
- In the Dynatrace menu, select Settings > Preferences > Data privacy and security.
- Enable the Mask end-user IP addresses & GPS coordinates option (enabled by default in new environments).
With this setting enabled, end user IP addresses & GPS coordinates are masked during Real User Monitoring and server-side monitoring. User IP addresses for web, mobile, custom applications, and services are masked when this feature is enabled. IP addresses are immediately masked as they are received by Dynatrace. They are masked before storage, never in their original form.
- To extend end-user privacy, the Mask all IP addresses option has been added. Selecting this option doesn't affect the existing settings. If you’ve previously masked your IP addresses, the option will be set to Mask only public IP addresses.
- For mobile apps, Dynatrace uses the coordinates from the device by using GPS or Wifi.
If the app has the permission to use this geolocation information, Dynatrace uses it to calculate the city that is closest to the reported GPS location. If not, Dynatrace uses MaxMind Geo2 Database.
Mask personal data in URIs
URIs contain personal data, such as a user names. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces these values with a placeholder.
Mask user actions
This setting only affects Real User Monitoring for web applications. With this setting enabled, no input data is captured. Instead, generic values are used as the basis for user action names. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:
- User event type (
loading of page..., or
- Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, check box, or text input field).
In most instances, the default approach to user-action naming works well, resulting in user-action names such as:
click on “Search” on page /search.html
keypress on “Feedback” on page /contact.html
touch on “Homescreen” of page /list.jsf
In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) may be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example,
click on “my Account Number: 1231231). If such confidential data appears in your application’s user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:
click on INPUT on page /search.html
keypress on TEXTAREA on page /contact.html
touch on DIV of page /list.jsf