Pure Storage FlashArray extension

  • Latest Dynatrace
  • Extension
  • Published Oct 27, 2025

Monitor your Pure Storage FlashArray alerts, capacity, and performance metrics.

Get started

Overview

Monitor multiple FlashArrays and aggregate these into a single dashboard, or group them together by customer-defined environments.

Pure Storage FlashArray overview

Pure Storage FlashArray overview

Use cases

  • View high-level array configuration.
  • Monitor performance metrics and configure alerts.
  • Correlate FlashArray metrics with other platforms.

Compatibility information

  • Purity version 6.1.0+: Some metrics may have been exposed in later versions of the Purity REST API 2.x and Pure Storage OpenMetrics exporter.

Exporter compatibility:

  • FlashArray version 6.6.11 and earlier: Requires the external exporter.
  • Purity version 6.7.0+: The OpenMetrics Exporter is integrated natively.

Activation and setup

To enable the extension, find Pure Storage FlashArray in the Dynatrace Hub.

To use this extension, Dynatrace will need to connect to the Pure Storage OpenMetrics exporter. This exporter receives requests for exposed metric endpoints and sends the request to the FlashArray via the REST API client. The REST results are interpreted and sent back to Dynatrace in the OpenMetrics standard format for ingestion.

The metrics exporter can be connected to in one of two ways:

Why are there two exporters?

Both exporters provide the same telemetry data, only the integrated version will receive feature request updates. It depends on your Purity version.

Check the compatibility section for latest information on specific Dynatrace prerequisites.

Set up the native metrics exporter

Purity FlashArray version 6.7.0+.

Metrics can be consumed directly from the array.

  1. Enable the extension, see Activation.

  2. At the top of this page, select the blue Add configuration button.

  3. Select ActiveGate.

  4. Select your deployed ActiveGate group capable of connecting to the FlashArray, then select Next.

  5. Configure your endpoints with the following information:

    • URL: https://arrayname01.fqdn/metrics/array?namespace=purefa
    • Authentication scheme: Bearer (token) authentication
    • Token: 111111-1111-1111-111111111111 (enter array token)
    • Press + Add endpoint to add additional metric endpoints.

  6. Select Next.

  7. Select Attributes.

    • Add a descriptive name for the configuration.
    • Select the required metric feature sets to be ingested.

  8. Select Save.

  9. Log inn to the Dynatrace ActiveGate which has access to the OpenMetrics Exporter. Restart the ActiveGate extensionsmodule service to download and enable the configuration.

    # systemctl restart extensionsmodule

  10. The status should change from Pending to Ok

  11. After a few minutes the status should show OK If Error is displayed, then check troubleshooting section.

The OpenMetrics Overview dashboard requires metrics from the following endpoints:

  • /metrics/array
  • /metrics/hosts
  • /metrics/volumes.

Alternatively, configure all metric endpoints and select metrics from the feature sets in the next page.

Configure Open Source Metrics Exporter

Purity FlashArray 6.6.11 and earlier

The external metrics exporter is a very lightweight binary/container which queries the array REST API and converts the response into a standardized open metrics format to be consumed by monitoring and observability platforms.

  1. Enable the extension, see Activation.

  2. At the top of this page, select Add to environment.

  3. In Configuration > Versions, select Add monitoring configuration.

  4. Select the Monitor remotely tab.

  5. In the ActiveGates section, select the appropriate ActiveGate group and then select Next step.

  6. In the Prometheus section, add configuration entries for each metric endpoint to be scraped.

    1. Select Add endpoint.

    2. Select the URL, according to the exporter:

      • Open Source Exporter URL: http://pure-ome-address:9490/metrics/array?endpoint=arrayname01
      • Native Exporter URL: http://array-address/metrics/array?namespace=purefa
      • TLS: use HTTPS

    3. Authentication scheme: In the drop-down menu, select No authentication.

    4. Skip ssl verification: Select the Skip ssl verification toggle so that it is enabled.

    Refrain from scraping all metrics using /metrics* as these are expensive queries in large environments.

  7. In the Finalize configuration section, check the configuration and select the required metric feature sets to be ingested into Dynatrace. Then, select Activate.

  8. Log in to the Dynatrace ActiveGate that has access to the OpenMetrics Exporter and restart the extensionsmodule service to download and enable the configuration.

    # systemctl restart extensionsmodule

  9. After a few minutes the configuration will appear with status Ok and metrics will be ingested.

Authentication

Dynatrace requires secure connections when using any kind of authentication. Pure Storage OpenMetrics Exporter must be configured with either

  • Insecure: http with API tokens.yaml file and no authentication.
  • Secure: TLS https with bearer token.

Dynatrace will not allow Pure Storage OpenMetrics Exporter to be configured with standard HTTP and bearer token.

If using TLS, ensure url is set to https. No further Dynatrace configuration is required if Skip ssl verification is enabled. Alternatively, the ActiveGate will require the certificate to be added to the OS trust store and ActiveGate collector configuration. For more information, see Determine the required CA certificates and prepare them as a file.

See Configure Pure Storage OpenMetrics exporter for configuration dependencies.

Metric endpoints and scrape intervals

Performance metrics are scraped as frequently as possible to capture trends in data. Other metrics are scraped less frequently to reduce the amount of metrics ingested into the platform.

By default, this extension scrape endpoints at predefined intervals as follows:

Feature SetDevice Metric EndpointScrape IntervalRequired for Fleet Overview dashboard
default/metrics/arrayone minuteYes
Alerts/metrics/arrayfive minutesYes
Directories/metrics/directoriesfive minutes
Hosts/metrics/hostsone minuteYes
HW/metrics/arrayfive minutes
Pods/metrics/podsone minute
Volumes/metrics/volumesone minuteYes

To customize these scrape intervals, contact your Dynatrace representative to configure a custom extension.

Details

The integration can provide performance data at the array, host, volume and pod level, as well as high-level capacity and configuration information.

This extension provides two integrated dashboards:

  • Pure storage overview (OpenMetrics) dashboard. Monitor your fleet of FlashArrays in one simple view, which displays:

    • Purity OS version.
    • Alerts and criticality.
    • Data reduction ratio.
    • Capacity utilization.
    • Data throughput.
    • IOPS by type.

    This dashboard requires certain metric endpoints and feature sets. For more information, see Metric endpoints and scrape intervals.

  • Pure storage entity overview dashboard. Drill down into individual FlashArray configurations and components.

Feature sets

When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.

In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.

All metrics that aren't categorized into any feature set are considered to be the default and are always reported.

A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.

Pods
Metric nameMetric keyDescription
PureFA Pod Mediator Statuspurefa_pod_mediator_statusFlashArray pod mediator status
PureFA Pod Performance Average Bytespurefa_pod_performance_average_bytesFlashArray pod average operations size
PureFA Pod Performance Bandwidth Bytespurefa_pod_performance_bandwidth_bytesFlashArray pod bandwidth
PureFA Pod Performance Latency Usecpurefa_pod_performance_latency_usecFlashArray pod latency
PureFA Pod Performance Replication Bandwidth Bytespurefa_pod_performance_replication_bandwidth_bytesFlashArray pod replication bandwidth
PureFA Pod Performance Throughput Iopspurefa_pod_performance_throughput_iopsFlashArray pod throughput
PureFA Pod Replica Links Lag Average Secpurefa_pod_replica_links_lag_average_secFlashArray pod links average lag seconds
PureFA Pod Replica Links Lag Max Secpurefa_pod_replica_links_lag_max_secFlashArray pod links max lag seconds
PureFA Pod Replica Links Performance Bandwidth Bytespurefa_pod_replica_links_performance_bandwidth_bytesFlashArray pod links bandwidth
PureFA Pod Space Bytespurefa_pod_space_bytesFlashArray pod space in bytes
PureFA Pod Space Data Reduction Ratiopurefa_pod_space_data_reduction_ratioFlashArray pod space data reduction
Network Interfaces
Metric nameMetric keyDescription
PureFA Network Interface Performance Bandwidth Bytespurefa_network_interface_performance_bandwidth_bytesFlashArray network interface bandwidth
PureFA Network Interface Performance Errorspurefa_network_interface_performance_errorsFlashArray network interface errors
PureFA Network Interface Performance Throughput Pktspurefa_network_interface_performance_throughput_pktsFlashArray network interface throughput
Directories
Metric nameMetric keyDescription
PureFA Directory Performance Average Bytespurefa_directory_performance_average_bytesFlashArray directory average operations size
PureFA Directory Performance Bandwidth Bytespurefa_directory_performance_bandwidth_bytesFlashArray directory bandwidth
PureFA Directory Performance Throughput Iopspurefa_directory_performance_throughput_iopsFlashArray directory throughput
PureFA Directory Performance Latency Usecpurefa_directory_performance_latency_usecFlashArray directory latency
PureFA Directory Space Bytespurefa_directory_space_bytesFlashArray directory space in bytes
PureFA Directory Space Data Reduction Ratiopurefa_directory_space_data_reduction_ratioFlashArray directory space data reduction
Volumes
Metric nameMetric keyDescription
PureFA Volume Space Bytespurefa_volume_space_bytesFlashArray volume space in bytes
PureFA Volume Performance Average Bytespurefa_volume_performance_average_bytesFlashArray volume average operations size
PureFA Volume Performance Bandwidth Bytespurefa_volume_performance_bandwidth_bytesFlashArray volume throughput
PureFA Volume Performance Latency Usecpurefa_volume_performance_latency_usecFlashArray volume latency
PureFA Volume Performance Throughput Iopspurefa_volume_performance_throughput_iopsFlashArray volume throughput
PureFA Volume Space Data Reduction Ratiopurefa_volume_space_data_reduction_ratioFlashArray volume space data reduction
HW
Metric nameMetric keyDescription
PureFA Hw Component Statuspurefa_hw_component_statusFlashArray hardware component status
PureFA Hw Component Temperature Celsiuspurefa_hw_component_temperature_celsiusFlashArray hardware component temperature
PureFA Hw Component Voltage Voltpurefa_hw_component_voltage_voltFlashArray hardware component voltage
Hosts
Metric nameMetric keyDescription
PureFA Host Connections Infopurefa_host_connections_infoFlashArray host volumes connections
PureFA Host Performance Average Bytespurefa_host_performance_average_bytesFlashArray host average operations size in bytes
PureFA Host Performance Bandwidth Bytespurefa_host_performance_bandwidth_bytesFlashArray host bandwidth in bytes per second
PureFA Host Performance Latency Usecpurefa_host_performance_latency_usecFlashArray host latency in microseconds
PureFA Host Performance Throughput Iopspurefa_host_performance_throughput_iopsFlashArray host throughput in iops
PureFA Host Space Bytespurefa_host_space_bytesFlashArray host space in bytes
PureFA Host Space Data Reduction Ratiopurefa_host_space_data_reduction_ratioFlashArray host space data reduction
Array
Metric nameMetric keyDescription
PureFA Array Performance Average Bytespurefa_array_performance_average_bytesFlashArray array average operations size
PureFA Array Performance Bandwidth Bytespurefa_array_performance_bandwidth_bytesFlashArray array bandwidth
PureFA Array Performance Latency Usecpurefa_array_performance_latency_usecFlashArray array latency
PureFA Array Performance Queue Depth Opspurefa_array_performance_queue_depth_opsFlashArray array queue depth size
PureFA Array Performance Throughput Iopspurefa_array_performance_throughput_iopsFlashArray array throughput
PureFA Array Space Bytespurefa_array_space_bytesFlashArray array space in bytes
PureFA Array Space Data Reduction Ratiopurefa_array_space_data_reduction_ratioFlashArray array space data reduction
PureFA Array Space Utilizationpurefa_array_space_utilizationFlashArray array space utilization in percent
Alerts
Metric nameMetric keyDescription
PureFA Alerts Openpurefa_alerts_openFlashArray open alert events
Drives
Metric nameMetric keyDescription
PureFA Drive Capacity Bytespurefa_drive_capacity_bytesFlashArray drive capacity bytes
default
Metric nameMetric keyDescription
PureFA Infopurefa_infoFlashArray system information

FAQs and troubleshooting

What is the DDU consumption of this extension?

To calculate your DDU cost per array, you need the following information:

  • Number of hosts

  • Number of pods

  • Number of volumes

  • Number of NICs

  • Number of hardware components

    • Number of temp sensors
    • Number of power supplies

  • Number of directories (filesystems)

Example formula:

(45 + (39 * hosts) + (56 * pods) + (38 * volumes)) * 525.6)
+
((10 * NICs) + total hardware components + temp sensors + power supplies + (26 * directories) + 2) * 105.12)
= Total DDUs/Year for the one FlashArray
  • The first piece of the equation (45 + (39 * Hosts) + (56 * Pods) + (38 * Volumes)) * 525.6) are for metric polled every one minute.
  • The second piece of the equation ((10 * NICs) + total hardware components + temp sensors + power supplies + (26 * directories) + 2) * 105.12) are for metrics polled every five minutes.
"GENERIC_ERROR:There is no endpoint that could have connected."

  • Symptoms:

    When scraping metrics, the following error occurs: Failed to assign monitoring configuration to ActiveGate. Reason: GENERIC_ERROR:There is no endpoint that could have connected.

  • Cause: The ActiveGate has not been successful in reaching the endpoint.

  • Resolution: There are a number things to check here:

    1. Check that the IP address or fully qualified domain name is reachable from the ActiveGate.

    2. Check that the connection is via HTTPS and not HTTP.

    3. Check the port number:

      • Native Exporter: There is no need to specify the port number. The default HTTPS port (443) will be used.
      • Open Source Exporter: Confirm the port number is correct.

    4. Confirm there are no typos in the endpoints, see Metric endpoints and scrape intervals.

"ERROR: Querying Native Array Exporter returns 'There are no queryMetrics defined in the extension'"

  • Symptoms: When scraping metrics, the following messages appear:

    INFO: There are no queryMetrics defined in the extension. Nothing to query Prometheus API for.

    ERROR:

    GENERIC_ERROR:Failed to query 'https://<array_address>/metrics/array?namespace=purefa/' for metrics: purefa_volume_space_bytes, purefa_volume_performance_average_bytes, purefa_volume_performance_bandwidth_bytes, purefa_volume_performance_latency_usec, purefa_volume_performance_throughput_iops, purefa_volume_space_data_reduction_ratio, purefa_network_interface_performance_bandwidth_bytes, purefa_network_interface_performance_errors, purefa_array_performance_average_bytes, purefa_network_interface_performance_throughput_pkts, purefa_array_performance_bandwidth_bytes, purefa_array_performance_latency_usec, purefa_array_performance_queue_depth_ops, purefa_array_performance_throughput_iops, purefa_array_space_bytes, purefa_pod_mediator_status, purefa_array_space_data_reduction_ratio, purefa_array_space_utilization, purefa_pod_performance_average_bytes, purefa_pod_performance_bandwidth_bytes, purefa_host_connections_info, purefa_host_performance_average_bytes, purefa_pod_performance_latency_usec, purefa_host_performance_bandwidth_bytes, purefa_pod_performance_replication_bandwidth_bytes, purefa_host_performance_latency_usec, purefa_host_performance_throughput_iops, purefa_pod_performance_throughput_iops, purefa_host_space_bytes, purefa_pod_replica_links_lag_average_sec, purefa_host_space_data_reduction_ratio, purefa_pod_replica_links_lag_max_sec, purefa_pod_replica_links_performance_bandwidth_bytes, purefa_pod_space_bytes, purefa_pod_space_data_reduction_ratio, Reason: Invalid content type  (https://<array_address>/metrics/array?namespace=purefa//query): text/html;charset=UTF-8 [status code=27];

  • Cause: The agent might be pointing to an array running Purity version 6.6.10 and earlier and the exporter is not available.

  • Resolution: Use the (external) Open Source OpenMetrics exporter, see pure-fa-openmetrics-exporter on GitHub.

`ERROR: Failed to query /metrics/directories`

  • Symptoms: The following errors are seen in the logs.

    • Error1:

      DEVICE_CONNECTION_ERROR:Failed to query 'http://pure-ome:9590/metrics/directories?endpoint=arrayname.fqdn/' for metrics:

    • Error 2:

      OK:Verified successfuly 5 of 5 Prometheus endpoint(s). Starting polling of verified endpoints. Non verified endpoints will be verified again in next interval.; DEVICE_CONNECTION_ERROR:Failed to query 'http://pure-ome:9590/metrics/directories?endpoint=arrayname.fqdn/'

  • Cause: FA file is not enabled on the array, therefore there are not file directories to list.

  • Resolution: Remove the endpoint query scraping /metrics/directories.

Hub

Explore in Dynatrace Hub

Monitor your Pure Storage FlashArray alerts, capacity, and performance metrics.

Related tags
StoragePrometheusStoragePure StorageInfrastructure Observability