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.uidfield) - Kubernetes version
- Platform (is it Kubernetes or Openshift)
- Is PMM enabled, and the PMM Version
- Operator version
- Mongo version
- Percona Backup for MongoDB (PBM) version
- Is sharding enabled (starting from the Operator version 1.13)
- Is Hashicorp Vault enabled (starting from the Operator version 1.13)
- Is the Operator deployed in a cluster-wide mode (starting from the Operator version 1.13)
- Is the Operator deployed with Helm
- Are sidecar containers used
- Are backups used, are point-in-time recovery and/or scheduled physical backup features used, if so
- How large is the cluster
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/psmdb-db --version 1.14.0 --namespace my-namespace --set disable_telemetry="true"
- if you don’t use helm for installation, you have to edit the
operator.yamlbefore applying it with thekubectl apply -f deploy/operator.yamlcommand. Open theoperator.yamlfile with your text editor, find the value of theDISABLE_TELEMETRYenvironment variable and set it totrue:
env:
...
- name: DISABLE_TELEMETRY
value: "true"
...
