Data and usage (Delphix Telemetry)

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 when your DCT installation uses online registration. If your DCT installation cannot maintain an online connection, follow the offline registration process and upload exports manually.

Telemetry registration and sharing anonymized telemetry data with Delphix are required for DCT. For registration and upload instructions, see Registration and Telemetry.

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 table describes the categories of data included in Delphix Telemetry exports. These categories apply to both online and offline uploads. You cannot select individual categories to include or exclude from a telemetry export.

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 Export Information	Anonymized customer identifier, timestamp of export 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.
Synthetic Data Generation	Usage information for Synthetic Data Generation, including reference-connector counts, target-connector relationships, generated row counts, discovery-method usage, generator overrides, and successful or failed executions. Generated row counts are aggregated for each telemetry upload window. If an upload covers a period since the previous upload, the export includes the applicable data for that interval. Generator override metrics are grouped by the field's current assignment method. This information is included in the existing Product Telemetry exports when telemetry sharing is enabled; no separate Synthetic Data setting is required.
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, submit a support request ticket to the Delphix Support Portal.