Enable the monitoring service

After installing PX-Central on-premises, follow the steps in this topic to enable the monitoring server component.


  • Deploy the PX-Backup chart, and ensure all components are in running state.

  • If you run Portworx on Openshfift, then add a new service account to the privileged SCC. Enter the oc edit scc privileged command and add the following line to the users section, replacing <YOUR_NAMESPACE> with your namespace.

  • Depending on how you access the px-backup-ui service, one of the following ports must be open:

    • HTTP port 80 - if you use an Ingress rule or a load balancer endpoint
    • Port specified in the spec.type:NodePort section of the px-backup-ui service - if you use the PX-Central endpoint
NOTE: Ensure the px-central-ui endpoint is accessible from pods that run PX-Central, to ensure that monitoring/grafana services are available.

Prepare air-gapped environments

If your cluster is internet-connected, skip this section. If your cluster is air-gapped, then pull the monitoring service and related Docker images to either your Docker registry or directly onto your nodes.

  1. Create a kube_version environment variable and assign your Kubernetes version to it.

    kube_version=`kubectl version --short | awk -Fv '/Server Version: / {print $3}'`
  2. Pull the following required Docker images onto your air-gapped environment.

    • docker.io/portworx/cortex:v1.1.0
    • docker.io/portworx/cassandra:3.11.6-debian-10-r153
    • docker.io/portworx/nginx:1.17
    • docker.io/portworx/consul:1.9.5-debian-10-r18
    • docker.io/portworx/go-dnsmasq:release-1.0.7
    • docker.io/portworx/grafana:7.1.3
    • docker.io/portworx/prometheus:v2.29.1
    • docker.io/portworx/configmap-reload:v0.0.1
    • docker.io/portworx/prometheus-config-reloader:v0.50.0
    • docker.io/portworx/prometheus-operator:v0.50.0
    • docker.io/portworx/memcached-exporter:v0.4.1
    • docker.io/portworx/memcached:1.5.7-alpine
    • docker.io/portworx/memcached:1.5.12-alpine
    • docker.io/portworx/px-operator:1.7.1

To pull the above Docker images and push them to an internal registry:

  1. Download the pxcentral-ag-install-monitor.sh air-gapped bootstrap PX-Central install script.

    curl -o pxcentral-ag-install-monitor.sh -L "https://install.portworx.com/pxcentral-air-gapped?px-monitor=true” 

    You can also download the install script for a specific release by specifying a version query. For example:

    curl -o pxcentral-ag-install-monitor.sh -L “https://install.portworx.com/pxcentral-air-gapped?version=2.0.1&px-monitor=true” 
  2. Pull the container images using the pxcentral-ag-install-monitor.sh script.

    ./pxcentral-ag-install-monitor.sh pull
  3. Push the images to a local registry server accessible by the air-gapped nodes. Replace <repo> with your registry location.

    ./pxcentral-ag-install-monitor.sh push <repo>

Enable the monitoring service

  1. Generate the install spec using the License Server and Monitoring spec generator. If you use Portworx to install PX-Central, select the Use storage class checkbox under the Configuration section of the Spec Details tab. In the Storage Class Name text box, enter the name of the storage class you used to install PX-Central.

    Select the Monitoring on PX-Central checkbox under Select Components section. Additionally, select the SSL Enabled checkbox if Portworx is SSl enabled.

    Select the Use custom registry checkbox under the Custom Registry section, and enter the following information:

    • Custom Registry: The hostname of your custom registry
    • Image Repository: The path to the required Docker images
    • Image Pull Secret(s) (Optional): A comma-separated list of your image pull secrets.

  2. Using Helm, add the Portworx Enterprise repository to your cluster and update it.

    helm repo add <repo-name> portworx http://charts.portworx.io/ && helm repo update
  3. Enable the monitoring service using either the --set flag or the values.yml file provided in the Step 2 section of the Complete tab of the spec generator.

Last edited: Tuesday, Mar 1, 2022