Telemetry¶

The Telemetry function enables the Operator gathering and sending basic anonymous data to Percona, which helps us to determine where to focus the development and what is the uptake for each release of Operator.

The following information is gathered:

ID of the Custom Resource (the metadata.uid field)
Kubernetes version
Platform (is it Kubernetes or Openshift)
PMM Version
Operator version
Percona XtraDB Cluster version
HAProxy version
ProxySQL version
Percona XtraBackup version
Is Operator deployed in a cluster-wide mode

We do not gather anything that identify a system, but the following thing should be mentioned: Custom Resource ID is a unique ID generated by Kubernetes for each Custom Resource.

Telemetry is enabled by default and is sent to the Version Service server when the Operator connects to it at scheduled times to obtain fresh information about version numbers and valid image paths needed for the upgrade.

The landing page for this service, check.percona.com, explains what this service is.

You can disable telemetry with a special option when installing the Operator:

if you install the Operator with helm, use the following installation command:

$ helm install my-db percona/pxc-db --version 1.12.0 --namespace my-namespace --set disable_telemetry="true"

if you don’t use helm for installation, you have to edit the operator.yaml before applying it with the kubectl apply -f deploy/operator.yaml command. Open the operator.yaml file with your text editor, find the value of the DISABLE_TELEMETRY environment variable and set it to true:

env:
  ...
  - name: DISABLE_TELEMETRY
    value: "true"
  ...

Contact Us

For free technical help, visit the Percona Community Forum.

To report bugs or submit feature requests, open a JIRA ticket.

For paid support and managed or consulting services , contact Percona Sales.

Last update: 2023-02-09