Observe Portworx PVCs and Disks for KubeVirt VMs

You can observe and manage Portworx-backed Persistent Volume Claims (PVCs) or Disks for KubeVirt virtual machines (VMs) from the Portworx tab in the OpenShift web console.

The Portworx tab on the VirtualMachine page in the OpenShift web console displays detailed information about each PVC, including performance metrics such as IOPS and throughput. When you create a virtual machine using OpenShift Virtualization, the console automatically displays the associated Portworx volume under this tab. This enables you to monitor storage performance directly within the OpenShift interface.
For information on how to create a StorageClass, PVCs, or a KubeVirt VM, see Manage storage for KubeVirt VMs.

Prerequisites

To enable the Portworx tab, your cluster must meet the following prerequisites:

• Run Portworx Enterprise 3.4.0 or later.
• Run OpenShift version 4.16 or later.
• Have OpenShift Virtualization enabled.
  For information on how to enable OpenShift Virtualization, see OpenShift documentation.
• Have the Portworx OpenShift Dynamic plugin enabled.
  For information on how to enable the Portworx console plugin, see Enable Portworx OpenShift Dynamic Plugin.
• Have Openshift Prometheus monitoring configured. For information on how to configure Prometheus monitoring, see Monitor Clusters on OpenShift.

The Portworx tab appears automatically when all the prerequisites are met. No additional user action is required.

View the Metrics

To view the metrics of a PVC attached to the KubeVirt VM, follow these steps:

1. Log in to the OpenShift web console.
2. From the left navigation pane, select Virtualization > VirtualMachines.
   The system displays the VirtualMachines page.
3. Select the VM to view the metrics.
   The system displays the VM details page.
4. Click the Portworx tab.
   The system displays the storage information of the PVC that contains the performance metrics and storage details.

PVC Metrics and Attributes

The following table lists the metrics and the attributes of the PVC that is displayed in the Portworx tab.

note

For FlashArray Direct Access (FADA) volumes and other storage backends where Portworx metrics are not collected, the Portworx tab does not display the performance metrics.

Metrics/Attributes	Description
IOPS	Displays the number of input/output operations per second for the PVC.
Throughput	Displays the data transfer rate, measured in kilobytes per second (KBps), for the PVC.
Latency	Displays the average time taken to complete I/O operations.
Usage Capacity	Displays total and used storage capacity for the PVC.
Alerts Affecting This Disk	Displays any active alerts related to the usage and health of the PVC.
Disk Details	Displays information about the virtual machine's associated storage. It includes metadata such as PVC name, underlying persistent volume, storage class used for provisioning, status of the data volume, and the node to which the volume is attached. It also displays the type of Attachment - Local or Remote. If the volume and the virtual machine instance are attached to the same node, the attachment type is shown as Local. If they are attached to different nodes, the attachment type is shown as Remote.
Portworx Volume Details	Displays metadata specific to the volume managed by Portworx. It includes details such as the volume name and unique volume ID, along with the current status of the volume (for example, attached or detached). This section also displays performance configuration settings, such as Application I/O control.
Replica Sets	Displays information about the individual replicas that make up a Portworx volume. It includes details such as name of the cluster node where the replica is hosted, unique identifier for the node within the Portworx cluster, the identifier of the specific storage pool on the node where the replica resides, and the current storage usage of the pool, shown in both absolute terms (GiB) and percentage. It also displays the overall Replication Status, which reflects whether all volume replicas are healthy and in sync. A status of Up confirms that replication is functioning normally across all nodes.