Personal data captured by Dynatrace

Dynatrace captures a lot of end-user data from monitored environments. Based on your license type and configuration, Dynatrace can capture both real-user traffic (user actions, captured directly in end-user browsers) and service-side traffic (web requests and other communications that may include personal data).

This page provides information about what personal data types Dynatrace collects (and why) for both Dynatrace Real User Monitoring (RUM) and server-side service monitoring. Here you'll also find information about how sensitive end-user data can be protected, including options for capturing such data by default or excluding it from capture.

Dynatrace Real User Monitoring (RUM)

Dynatrace helps you to improve performance and to both analyze and improve the user experience of your web applications and mobile apps. This includes automatic discovery of client errors and capabilities that detect the root causes of such errors in conjunction with Dynatrace OneAgent. Dynatrace does this by collecting data from the end users of your applications. This is done using client-side JavaScript or the OneAgent for Mobile SDK for native mobile apps.

Session Replay

With Dynatrace Session Replay, you can capture and visually replay the complete digital interaction of users with your application while also ensuring that your organization remains GDPR-compliant. Session Replay offers several configuration settings that can be applied to your application. Configure Session Replay for personal data protection to ensure that your customers' personal data is always protected.

Service request monitoring

Dynatrace helps you to improve the performance of your applications, it also enables you to analyze problems that occur in production in a timely manner. This is done via Dynatrace OneAgent.

Log Monitoring

With Dynatrace Log Monitoring, you gain direct access to the log content of all your system's mission-critical processes. It's easy to search for specific log messages that you're interested in. Log content can be filtered based on keywords or timeframe. You can even analyze multiple log files simultaneously—even when log files are stored across multiple hosts.

Most significantly, Dynatrace artificial intelligence automatically correlates relevant log messages with any problems that it detects in your environment. Relevant log messages that are associated with problems are then factored into problem root-cause analysis.

Summary of personal data capture scenarios

The following table provides an overview of how data that may include sensitive values may be captured by Dynatrace. Following are definitions of the various scenarios:

  • May contain PII data: PII data may be captured, either intentionally or accidentally.
  • Configurable capture: Data capture is configurable. Data may or may not be captured.
  • Captured by default: This data is captured by default.
  • Masked by default: If captured, the data is masked by default.
  • Masking on display: If captured, the data is masked on display by default.
  • Masking on storage: If captured, the data is masked before storage by default.
  • Masking on capture: If the data is captured and masking is enabled, the data is masked upon capture.
Product feature Data captured May contain PII data Configurable capture Captured by default Masked by default Masked at display Masked at storage Masked at capture Comment
Real User User clicks yes no yes no no configurable no
Real User URL yes no yes no configurable configurable no
Real User IP and Location yes no yes yes no configurable no
Session Replay User input yes yes yes no yes yes yes
Session Replay Images yes yes yes no yes yes yes
Session Replay Content yes yes yes no yes yes yes
Session Replay Attributes yes yes yes no yes yes yes
Session Replay Form fields yes yes yes yes yes yes yes
Session Replay Interactions yes yes yes no yes yes yes
Server side requests URL yes no yes no no configurable no
Server side requests URL Query parameter yes yes yes yes yes configurable no ³
Server side requests Client IP yes no yes yes yes configurable no
Server side requests HTTP request/response header yes yes only some no yes configurable no ¹
Server side requests HTTP post parameter yes yes no no yes configurable no ²
Server side requests Exception messages yes yes yes no yes no yes
Server side requests Method arguments/return values yes yes no no yes no no ²
Server side requests SQL literals and bind variables yes no no yes no no yes
  1. Only certain headers are captured automatically. All others are only captured when requested by an authorized user (see request attributes). The data that are captured aren't masked by default.
  2. All values are captured when requested by an authorized user (see request attributes)
  3. Query parameters are always confidential (masked on display) and can additionally be masked upon storage. They can be explicitly captured by request attributes, in which case their confidentiality depends on request attribute configuration.
  4. Dynatrace looks for personal data like IP addresses, UUIDs, credit card numbers, emails and other clearly indentifiable IDs. But there might be some other personal data of individual character that Dynatrace isn't able to detect automatically. You can mask the URL on display with custom names for user actions and resource grouping, or naming.
  5. Although password fields are form fields, their masking can't be disabled.
  6. By configuring your application for Session Replay, you can decide which content needs to be masked. If the content is configured to be masked at capture, it will also be masked at storage and at display. If configured differently, the content will be stored and displayed exactly as it was captured.