Manage Telemetry

Requirements to manage telemetry

To manage Pure1 telemetry, ensure that the following prerequisites are met:

• Portworx Backup 3.0.0 or later is installed.
• Telemetry was enabled during installation using telemetry.enabled=true in the Helm values. For more information, see Enable telemetry. The ConfigMap approach described in this topic only controls data collection for an already-enabled telemetry deployment. If telemetry was not enabled via Helm, updating the ConfigMap has no effect.

Manage telemetry data collection

You can enable or disable telemetry data collection and upload in Portworx Backup by updating the px-backup-config ConfigMap, without requiring a pod restart. Portworx Backup automatically picks up the ConfigMap changes during the next scheduled interval. For more information about the ConfigMap and how to update it, see Configure px-backup-config ConfigMap.

• Enable telemetry data collection

  kubectl -n <pxb-namespace> patch configmap px-backup-config --type merge \
    -p '{"data":{"TELEMETRY_COLLECTION_ENABLED":"true"}}'

• Disable telemetry data collection

  kubectl -n <pxb-namespace> patch configmap px-backup-config --type merge \
    -p '{"data":{"TELEMETRY_COLLECTION_ENABLED":"false"}}'

Disable telemetry through Helm upgrade

To fully disable telemetry and remove the telemetry pods from the cluster, use helm upgrade with telemetry.enabled=false:

helm upgrade px-central portworx/px-central \
  --namespace <pxb-namespace> \
  --set telemetry.enabled=false \
  -f values.yaml

note

Ensure that the same values.yaml used during installation is provided during the Helm upgrade.

This removes the telemetry pods from the <pxb-namespace> namespace. Unlike the ConfigMap approach, this stops telemetry until you re-enable it via Helm.

note

If you disable telemetry and later re-enable it, Portworx Backup resumes data upload using the existing Pure1 registration and signed certificate. A full re-registration with Pure1 is not required unless the certificate has expired.