Skip to content

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)
  • Is PMM enabled, and the PMM Version
  • Operator version
  • PostgreSQL version
  • PgBackRest version
  • Was the Operator deployed with Helm
  • Are sidecar containers used
  • Are backups used

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:

$ helm install my-db percona/pg-db --version 2.2.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 disable_telemetry key and set it to true:
...
disable_telemetry: "true"
...

Get expert help

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services. Join K8S Squad to benefit from early access to features and “ask me anything” sessions with the Experts.

Community Forum Get a Percona Expert Join K8S Squad

Last update: 2023-09-20