From monitored environments, Dynatrace may capture end-user data, potentially including personal and confidential information about your end users.
This page identifies where personal data may be captured and how you can limit the capture, storage, and display thereof to help you comply with privacy-related legal requirements, including the California Consumer Privacy Act (CCPA; California, United States), General Data Protection Regulation (GDPR; European Union), or Lei Geral de Proteção de Dados (LGPD; Brazil).
Dynatrace masks data according to our three levels of data protection: at capture, at storage, and at display. The following sections describe, for each data type, whether Dynatrace captures it by default, whether it's masked, and where you can change that.
Dynatrace captures the most important data points of incoming requests as well as the web requests of end-users of your application (that is, service requests). URLs, client IPs, and certain HTTP header fields are captured automatically.
You can configure global privacy settings to mask client IP addresses, URIs, and HTTP post parameters.
| Data type | Captured by default | Masked by default | Configurable masking |
|---|---|---|---|
Client IP addresses | Yes | Yes | At capture and storage1 |
URIs | Yes | No | At capture and storage2 |
HTTP headers | Yes, certain headers only3 | No | At storage2 |
HTTP post parameters | No | No | At storage2 |
URL query parameters4 | Yes | No | At capture and storage2 |
Exception messages5 | Yes | No | At capture and storage2 |
SQL literals6 | Yes | Yes, always | Not configurable |
SQL bind variables7 | No | No | Not configurable |
Method arguments / return values8 | No | No | Not configurable |
At display, all of these data types except URIs and SQL literals are visible only to users with the View sensitive request data permission. Other users see ***** instead. URIs are displayed as they were stored, and SQL literals are always masked.
Configure masking via the Mask end-user IP addresses and GPS coordinates option in the data privacy settings.
Configure masking at capture via the OneAgent-side masking option and masking at storage via the Mask personal data in URIs option in the data privacy settings.
Only certain headers are captured automatically. You can capture other headers via request attributes.
Query parameters are always masked on display and can also be masked upon storage. To capture parameters explicitly, configure request attributes.
To avoid capturing certain exceptions, go to
Settings > Collect and capture > Distributed tracing > Deep monitoring, expand the Exclude noisy and unnecessary exceptions section, and add the required exclusion rules.
Literals that are part of the WHERE clause of an SQL statement are replaced with *****, for example, WHERE userId = '*********'.
Bind variables support is available for database monitoring. To learn how to start capturing SQL bind values, see Data collected with Dynatrace database monitoring. SQL bind values are replaced with *****. Only users who have permission to view a specific entity or management zone can view unmasked bind values within that entity or zone.
Configure via request attributes.
Dynatrace automatically captures all OpenTracing and OpenTelemetry attributes, but it only stores attributes that are not blocked. Non-blocked attribute values are stored without masking, and only users with the required permissions can view them. See Enable the OpenTelemetry Span Sensor for OneAgent.
For the personal data that RUM and Session Replay capture, and how to mask it, see RUM data privacy and compliance.
Log Monitoring is an optional feature that is enabled by default. You can use it to directly access the log content of all your system's mission-critical processes, search for specific log messages, and store all logs centrally.
Log files can include user names, email addresses, URL parameters, and other information that you might not want to disclose. By default, nothing is masked, but Log Monitoring offers the ability to mask sensitive information in the logs. You define the masking rules, so any data can be replaced with an SHA-1 hash or a fixed phrase, for example, *****, #######, MASKED, or Last name.
You can apply masking rules in the OneAgent configuration, so data is masked before it leaves the monitored host, or during log processing in Dynatrace.
OneAgent diagnostics is an optional feature that enables you to collect and analyze support archives for anomalies.
Support archives are created by Dynatrace OneAgent and contain OneAgent log and configuration files as well as specific data from monitored hosts and processes, for example, process names and identification numbers. OneAgent log files may contain personal data, for example, as part of a stack trace. OneAgent doesn't mask these files when it creates a support archive; Dynatrace masks them before storage, as described below.
To comply with regional data protection and privacy regulations, Dynatrace does the following:
Masks some personal data before storing a support archive in Cassandra and uploading it to an AWS S3 bucket. For example, IBANs and URI credentials are replaced with <masked>. However, some personal data may not be masked.
Writes audit log messages when support archives are created, analyzed, accessed, and deleted to ensure transparency in the use of support archives.
Provides access to OneAgent support archives only to users that have the View sensitive request data environment permission.
Automatically deletes all diagnostic data 30 days after its collection.
This applies to the data in your Dynatrace environment. You can also choose to delete collected diagnostic data earlier.
Live Debugger is an optional feature. To make it available, enable Live Debugger on your OneAgents. You can use Live Debugger to debug your services and applications in any environment in real time without stopping your applications.
Live Debugger collects snapshots that can include variable values that your application processes. You can define masking rules, so any data can be replaced with an SHA-256 hash or a fixed phrase, for example, *****, #######, MASKED, or Last name. Masking is performed by the agent on your server, so sensitive data will not leave your server or network.