Configure the Prometheus receiver to collect NetApp metrics

Configure the Prometheus receiver to collect NetApp metrics.

You can monitor the performance of NetApp storage resources the following NetApp tools:

  • NetApp Trident: A storage orchestrator and management tool for containers and Kubernetes distributions.

  • NetApp Harvest: An open-metrics endpoint for ONTAP, StorageGRID, E-Series and Cisco Nexus switches.

Splunk Observability Cloud uses the Prometheus receiver to collect metrics from NetApp Trident and Harvest, which expose /metrics endpoints that publish Prometheus-compatible metrics.

This data integration requires:

  • A Kubernetes or OpenShift cluster with NetApp Trident installed.

  • Trident metrics exposed from the trident-csi service. Trident exposes Prometheus metrics at /metrics, typically on port 8001.

  • NetApp Harvest deployed and configured to collect ONTAP metrics from NetApp clusters.

  • NetApp Harvest configured with ONTAP cluster connection details and appropriate ONTAP API credentials.

  1. Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
  2. Activate the Prometheus receiver for NetApp Trident and NetApp Harvest manually in the Splunk Distribution of the OpenTelemetry Collector configuration by making the following changes to your values.yaml configuration file.
    1. Add the prometheus/trident and prometheus/netapp-harvest receivers to the receiver_creator/cisco_ai_pods section. For example:
      YAML 
      receiver_creator/cisco-ai-pods:
  watch_observers:
    - k8s_observer

  receivers:
    prometheus/trident:
      rule: type == "pod" && labels["app"] == "controller.csi.trident.netapp.io"
      config:
        config:
          scrape_configs:
            - job_name: trident-metrics
              scrape_interval: 10s
              metrics_path: /metrics
              static_configs:
                - targets:
                    - '`endpoint`:8001'

    prometheus/netapp-harvest:
      rule: type == "pod" && labels["app"] == "netapp-harvest"
      config:
        config:
          scrape_configs:
            - job_name: netapp-harvest-metrics
              scrape_interval: 30s
              metrics_path: /metrics
              static_configs:
                - targets:
                    - '`endpoint`:12990'
    2. Adjust the Harvest rule label selector if your Harvest pods use a different label, such as app.kubernetes.io/name, component, or service.name.
    3. Add the receiver_creator/cisco-ai-pods receiver in the metrics pipeline of the service section, if it's not already present. For example:
      YAML 
      service:
  pipelines:
    metrics/cisco-ai-pods:
      receivers:
        - receiver_creator/cisco-ai-pods
      processors:
        - memory_limiter
        - batch
        - resourcedetection
        - resource
      exporters:
        - signalfx
  3. Use Helm to apply the configuration changes:
    CODE 
    helm upgrade ucs-otel-collector \ 
--set="clusterName=$CLUSTER_NAME" \ 
--set="environment=$ENVIRONMENT_NAME" \ 
--set="splunkObservability.accessToken$SPLUNK_ACCESS_TOKEN\ 
--set="splunkObservability.realm=$SPLUNKREALM" \ 
--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

NetApp storage monitoring in Splunk Observability Cloud uses two main metric sources:

  • NetApp Harvest: Used for ONTAP cluster, controller, aggregate, volume, latency, throughput, network, and hardware/environment telemetry.

  • NetApp Trident: Used for Kubernetes/OpenShift CSI orchestration telemetry such as volume count, operation count, latency, failures, and backend health.

The following metrics are available for NetApp. For more information about these metrics, see Monitor Trident and ONTAP Metrics in the NetApp documentation.

These metrics are considered custom metrics in Splunk Observability Cloud.

Metric name Description
trident_backend_count The total number of backends.
trident_node_count The total number of nodes.
trident_operation_duration_milliseconds_count The total count of observed operations.
trident_operation_duration_milliseconds_quantile The latency quantile for operation events.
trident_operation_duration_milliseconds_sum The total duration of all observed operations.
trident_storageclass_count The total number of storage classes.
cluster_new_status The current cluster status.
cluster_subsystem_outstanding_alerts The current unresolved subsystem alert count.
node_avg_processor_busy The average processor busy percentage.