Configure the Prometheus receiver to collect Pure Storage metrics

Configure the Prometheus receiver to collect Pure Storage metrics from Portworx.

Cisco AI PODs are designed to integrate with high-performance storage solutions. You can monitor the performance of Cisco AI PODs that use Pure Storage with Portworx. Porworx is a Kubernetes data services platform that provides persistent storage, data protection, and disaster recovery for containerized applications.

Splunk Observability Cloud uses the Prometheus receiver to collect metrics from Portworx, which exposes a /metrics endpoint that publishes Prometheus-compatible metrics.

To configure the Prometheus receiver to collect Portworx metrics, you must meet the following requirements:
  1. Activate the Prometheus receiver for Portworx manually in the Splunk Distribution of the OpenTelemetry Collector configuration by making the following changes to your values.yaml configuration file.
    1. Add prometheus/portworx to the receiver_creator/cisco_ai_pods section. For example:
            receiver_creator/cisco-ai-pods: 
        # Name of the extensions to watch for endpoints to start and stop. 
        watch_observers: [ k8s_observer ] 
        receivers: 
          prometheus/portworx: 
            config: 
              config: 
                scrape_configs: 
                  - job_name: portworx-metrics 
                    static_configs: 
                      - targets: 
                        - '`endpoint`:17001' 
                        - '`endpoint`:17018' 
             rule: type == "pod" && labels["name"] == "portworx"
    2. Add the receiver_creator/cisco-ai-pods receiver to the metrics pipeline of the service section, if it's not already present. For example:
      metrics/cisco-ai-pods: 
  exporters: 
    - signalfx 
  processors: 
    - memory_limiter 
    - batch 
    - resourcedetection 
    - resource 
  receivers: 
    - receiver_creator/cisco-ai-pods
  2. Use Helm to apply the configuration changes: 
    helm upgrade ucs-otel-collector \ 
--set="clusterName=$CLUSTER_NAME" \ 
--set="environment=$ENVIRONMENT_NAME" \ 
--set="splunkObservability.accessToken=$SPLUNK_ACCESS_TOKEN" \ 
--set="splunkObservability.realm=$SPLUNK_REALM" \ 
--set="splunkPlatform.endpoint=$SPLUNK_HEC_URL" \ 
--set="splunkPlatform.token=$SPLUNK_HEC_TOKEN" \ 
--set="splunkPlatform.index=$SPLUNK_INDEX" \ 
-n otel \ 
-f ./base-otel-collector-config/values.yaml \ 
splunk-otel-collector-chart/splunk-otel-collector

Configuration settings

Learn about the configuration options for the Prometheus receiver.

To view the configuration options for the Prometheus receiver, see Settings.

Metrics

The following metrics are available for Pure Storage. These metrics fall under the default metric category.

For more information on these metrics, see Portworx Metrics for monitoring in the Portworx documentation.
Metric nameDescription
px_cluster_cpu_percentPercentage of CPU used.
px_cluster_disk_total_bytesTotal storage space in bytes for this node.
px_cluster_disk_utilized_bytesUtilized storage space in bytes for this node.
px_cluster_status_nodes_offlineNumber of offline nodes in the cluster (includes storage and storageless).
px_cluster_status_nodes_onlineNumber of online nodes in the cluster (includes storage and storageless).
px_volume_read_latency_secondsAverage time spent per successfully completed read operation in seconds for this volume.
px_volume_reads_totalTotal number of successfully completed read operations for this volume.
px_volume_readthroughputNumber of bytes read per second during this interval for this volume.
px_volume_write_latency_secondsAverage time spent per successfully completed write operation in seconds for this volume.
px_volume_writes_totalTotal number of successfully completed write operations for this volume.
px_volume_writethroughputNumber of bytes written per second during this interval for this volume.