Delphix Telemetry: Data and usage

Delphix Administrators help improve the performance, reliability, and usability of the platform by sharing anonymized telemetry data. This information provides the Delphix team with valuable insights into real-world usage patterns, which further enables Delphix to identify common challenges, prioritize feature enhancements, and proactively address potential issues. The gathering and use of this anonymized information ultimately leads to a better user experience for all Delphix customers.

Telemetry exports are automatically shared with Delphix daily if your Delphix Administrator has enabled the online registration mode for Data Control Tower (DCT). If you want to disable this behavior but still register your DCT instance and upload exports occassionally, follow the offline registration process.

Registration and sharing anonymized telemetry data with Delphix is highly recommended (but not required) to get the full benefit of DCT and your Delphix Account Team.

Security

Shared data is stored in Delphix’s AWS and Azure US West repositories and retained in accordance with Delphix’s data retention policies.

Penetration testing is performed regularly against the complete Delphix Telemetry solution. DCT is regularly tested as it manages various potentially sensitive metadata and builds the telemetry export. The Delphix Telemetry service is a part of Delphix Compliance Services (DCS), and thus, appropriate penetration testing is performed alongside that product set’s regular testing cycle.

For more information, please contact Perforce Security.

Shared data

The following data is shared within all telemetry export uploads. The same type of data is collected in each online or offline export. Today, the ability to select which data to include or exclude in a telemetry export is not supported.

The Telemetry Export does not include information typically found in the Support Bundle, such as the logs. Therefore, exports are far smaller in size (~10-20 MB) than a normal Support Bundle. Telemetry data is not shared as part of the Support Bundle.

Name	Description
General Bundle Information	Anonymized customer identifier, timestamp of bundle generation, and the time range of the data contained within.
DCT Product Information	Anonymized DCT system identifier, current product version, current API version, and database type/version.
DCT Product History	Full DCT version and platform installation (ex AWS, Azure, K8s, etc) history.
Registered Engines	Count of registered engines, engine type (Data, Compliance, etc), versions, platform, storage, network, and resource details.
API Telemetry	All API calls made via DCT, including Endpoint, Method, Start/End Times, Response Status, User Agent, and Client Name. For example: POST /vdbs/provision_vdb_by_snapshot, 1:00pm EST, 1:10pm EST, 200, Delphix-ServiceNow-Integration, service-client API payloads containing potentially sensitive data, such as virtual database configuration or connection credentials, are not collected.
Object Counts	Various counts across the platform, such as number of Connections, VDBs, dSources, Environments, Snapshots, Bookmarks, Masking Jobs, Profiling Jobs, Users, Engine Storage Breakdown, etc.
Object Details	Notable anonymized, object details that describe details that are critical to maintain proper support, including the data’s platform, version, infrastructure, infrastructure version, ingestion mechanism, and source sizes. For example: Connection, VDB, and dSource platform type and version (ex: Oracle 19c, SQL Server 2022, PostgreSQL 15.1, etc) dSource ingestion (ex: Direct, Staging Pull via <TYPE>, Staging Push) Source, Staging, and Target Infrastructure OS and Version (ex: RHEL 9.4) Oracle Database’s size (ex: 5.2 TB)

Deletion of Data

To request deletion of your organization’s telemetry data, please disable your automatic online uploads. If the telemetry data is still enabled, please submit a support request ticket to the Delphix Support Portal.