Data privacy and exchange in Managed deployments
Dynatrace Managed cluster administrators have access to a number of data-privacy settings that may affect the sharing of personal or confidential end-user data.
- See data data privacy section for information on privacy settings that suit your organization's needs.
All Dynatrace Managed clusters exchange information with Dynatrace Mission Control, at least once, or periodically.
- See data exchange section for information on data that Dynatrace receives from and pushes to your clusters.
You may want to opt-out of certain communications, such as allowing Dynatrace to proactively access your clusters and environments. However, some messages are mandatory and can't be switched off.
| Category | Data exchange | Opt out |
|---|---|---|
Pro-active support | Report usage and billing information. | No |
Pro-active support | Report Dynatrace cluster health. | No |
Dynatrace support resources | Environment identifiers and names | No |
Dynatrace support resources | Synchronize users' e-mail addresses2, first and last name, assigned permissions | Yes |
Pro-active support | Report cluster and OneAgent events to Dynatrace Mission Control. | Yes1 |
Pro-active support | Dynatrace deployment health monitoring. | Yes1 |
Pro-active support | Allow Dynatrace ONE remote access to environment monitoring settings. | Yes1 |
Pro-active support | Allow Dynatrace ONE to change your configuration. | Yes1 |
Privacy | Send information about monitored technologies and feature usage. | Yes |
Privacy | Use Mission Control as email notifications sender. | Yes |
Dynatrace support resources | Send users invitation to create a Dynatrace account on first login. With an account, users will have access to Dynatrace Community, Dynatrace University, and support tickets. | Yes |
Dynatrace support resources | Include results from Dynatrace Documentation in the platform search. | Yes |
Domain name and SSL certificates | Enable management of domain name and SSL certificates. | Yes |
This setting varies depending on your licensing. If this setting is disabled and you want to adjust it, contact Dynatrace ONE.
Affects users with a permission Cluster administrator, View product usage & manage account info, Access account, or Manage support tickets. Additionally, email addresses of emergency contacts and admin user account.
Data privacy
Dynatrace enables you to adjust data privacy settings to your organization needs by Cluster preferences settings. To ensure GDPR compliance, you must be aware of what personal data is captured by Dynatrace and you must configure Dynatrace to protect personal data.
Data exchange
The following information transparently documents the mandatory data that Dynatrace receives from your Dynatrace Managed cluster. Note that all communication between clusters and Mission Control is encrypted and always cluster-initiated only. Dynatrace isn't able to initiate a connection to customer clusters.
Installation
Frequency: Once during installation and during every upgrade
Cluster request: License key
Mission Control response: Account name, license name, OneAgent installation flag (true/false), OneAgent download URL
Registration
Frequency: Once (after first startup)
Cluster request: License key, cluster ID
Mission Control response: Registration status, username, password
License
Frequency: Once every 5 minutes
Cluster request: No cluster request
Mission Control response: License status, cluster ID, license key, license details, license model
Health check
Frequency: Once every 2 minutes
Cluster request: Cluster ID, privacy settings, time zone, traffic size, update/maintenance window. Each cluster node adds technical details including OS name and version, number of CPU cores, CPU load, total RAM, free RAM, total disk storage, used storage, server state, seed node flag (true/false), and startup timestamp. Each Cluster ActiveGate adds its version, OS name and version, status, certificate issuer, and type (e.g., beacon forwarder).
Mission Control response: Health status, message
Consumption
Frequency: Once each hour
Cluster request: Cluster ID, consumption timeframe. Each environment adds the number of new problems, RUM sessions, synthetic monitors. Every host adds a category, a list of monitored technologies, and monitoring timeframes. For each synthetic monitor, the ID, description, type, success count, failure count and action count are transmitted. See Export licensing data.
Mission Control response: Status, remaining RUM sessions, consumed RUM overage, host units overage, remaining synthetic monitors, consumed synthetic monitors overage. For each environment, its ID, consumed RUM sessions, consumed synthetic monitors, and host units are returned.
Heartbeat
Frequency: 20 requests every 10 minutes, or 12 requests every 10 minutes if remote access is disabled.
Cluster request: Cluster ID, node ID, source type (e.g., server)
Mission Control response: Remote UI request flag (true/false), Websocket URLs
Environment synchronization
Frequency: Synchronization difference: every 10 minutes. Full synchronization: once a day.
Cluster request: Environment ID, environment name
Updates
Frequency: Once each hour
Cluster request: No cluster request
Mission Control response: For cluster updates: version, description, download URL, size. For OneAgent and JavaScript tag updates: label, version, download URLs. For ActiveGate updates: label, version, download URLs
Dynatrace Hub
Frequency: Every 30 to 60 minutes.
Cluster request: No cluster-specific exposure, no personal data.
Mission Control response: Images and text describing the capabilities and extensions available in Dynatrace Hub.
Vulnerability feeds
Application Security searches for vulnerabilities in your environment based on vulnerability feeds.
Frequency: When updates are available
Cluster request: Vulnerability feed data
Mission Control response: Vulnerability feed data
We never send host names or other information that may compromise your cluster's security.