Enable Pure1 integration for upgrades

This page covers enabling Pure1 integration for the following cases:

• You had a running Portworx cluster prior to Portworx 2.8.0, and you are now upgrading to 2.12.0 or later
• You installed Portworx 2.12.0, but did not enable Pure1 integration and want to do so now

Prerequisites

• Portworx Operator 1.10.0 or later
• A cluster running Portworx 2.12.0 or using an Operator-based installation
• Outbound access to the internet to allow connection to Pure1

note

If you're using a daemonset-based Portworx installation, you must migrate to an Operator-based install, then:

• If you did not previously enable telemetry for your daemonset-based installation, upgrade to version 2.12 before enabling Pure1 integration.
• If you previously enabled telemetry for your daemonset-based installation, when you migrate that to an Operator-based installation, telemetry is still enabled.

Enable telemetry

Additional configuration for air-gapped clusters

In air-gapped clusters, telemetry is supported via simple or traditional proxy that serves in HTTP mode. If you have a next generation firewall acting as a proxy, or have a problem with the telemetry configuration, contact Portworx Support for assistance.

To enable telemetry, configure a proxy and add it to the PX_HTTP_PROXY or PX_HTTPS_PROXY environment variable in your StorageCluster specification. Telemetry communicates through the specified proxy.

StorageCluster

...
spec:
  env:
    - name: PX_HTTP_PROXY
      value: "http://<IP:port>"
    - name: PX_HTTPS_PROXY
      value: "http://<IP:port>"
...

Portworx supports telemetry in the StorageCluster spec, but it's disabled by default. To enable the metrics collector and telemetry integration with Pure1, add the following section in your StorageCluster spec:

spec:
  monitoring:
    telemetry:
      enabled: true 

This adds telemetry components to Portworx and automatically creates the pure-telemetry-certs secret in the <px-namespace> namespace. You can also enable telemetry from Portworx Central via Advanced Settings on the Customize page.

Metrics collector configuration

Starting with Portworx Operator 25.5.2, you can configure the metrics collector separately from other telemetry components.

The metrics collector requires telemetry to be enabled. When telemetry is enabled, the metrics collector is enabled by default. You can disable the metrics collector while keeping telemetry enabled, but you cannot enable the metrics collector without telemetry.

When telemetry is enabled, the Operator automatically adds metricsCollector.enabled: true to your StorageCluster spec. If you use GitOps to manage your StorageCluster, ensure your Git manifest includes this field so that your Git repository matches the actual cluster state.

The telemetry metrics collector scrapes Prometheus metrics from Portworx pods, forwards these real-time metrics to Pure1 for monitoring and analytics, and provides data for Pure1 dashboards showing capacity, utilization, and performance trends.

When you disable the metrics collector, real-time metrics forwarding to Pure1 stops, which means Pure1 dashboards no longer display current metrics. However, diagnostics upload to Pure1 continues to work, and support functionality remains intact. Pure1 AI Copilot continues to function because it uses diagnostics data. Your own Prometheus monitoring solutions continue to work normally because Portworx continues exporting metrics locally.

Disable metrics collector while keeping telemetry enabled:

spec:
  monitoring:
    telemetry:
      enabled: true
      metricsCollector:
        enabled: false

This configuration disables real-time metrics forwarding to Pure1 but maintains diagnostics uploads for support purposes.

Use a custom image for the metrics collector:

spec:
  monitoring:
    telemetry:
      enabled: true
      metricsCollector:
        enabled: true
        image: "portworx/realtime-metrics:<version>"

This configuration allows you to deploy a specific version or hotfix image for the metrics collector.