Everpure (formerly Pure Storage) FlashArray Monitoring
Last updated – 19 August, 2026
Disclaimer: Pure Storage is now Everpure. References to Pure Storage documentation in this content link to the corresponding Everpure documentation.
For more information, see Pure Storage Is Now Everpure from Everpure.
LogicMonitor’s Everpure (formerly Pure Storage) FlashArray Monitoring package provides visibility into the health, capacity, performance, and availability of Pure Storage FlashArray systems.
The package uses the FlashArray REST API to collect monitoring data, with optional SNMP-based monitoring available for overall array performance statistics.
For more information, see REST API 1.12 from Everpure.
Requirements for Everpure (formerly Pure Storage) FlashArray Monitoring
To use Pure Storage FlashArray monitoring, you need the following:
- A LogicMonitor user with Read-only permissions to resources in the Modules role permissions
- An Everpure FlashArray account with access to the resourceNote: Depending on your Everpure FlashArray configuration, this account can be created locally on the resource or managed through an Active Directory or LDAP integration.
- A Pure Storage API Token
For more information, see Configuring Everpure (formerly Pure Storage) FlashArray Credentials. - The following PropertySources installed in LogicMonitor:
addCategory_PureStoragePureStorage_ArrayInfoPureStorage_API_Versions
For more information, see Resource and Instance Properties.
Configuring Everpure (formerly Pure Storage) FlashArray Credentials
- In Pure Storage, create an API token for the Everpure user account using one of the following methods:
- Graphic User Interface (GUI)
For more information, see Rest API Setup through the Graphic User Interface (GUI) from Everpure. - Command-line interface
Use the following command:For more information, see Pure Storage REST API + Windows PowerShell from Everpure.pureadmin create --api-token
- Graphic User Interface (GUI)
- Copy the generated API token and save it to a secure location.
The API token looks similar to the following:523eb429-7432-3425-bb12-5fe45ba66416 - In LogicMonitor, add the API token to the monitored resource as the following resource property:
| Resource Property | Value |
|---|---|
purestorage.apitoken.pass | The API token generated in Everpure |
For more information, see Adding API tokens.
The Everpure resource is now associated with your LogicMonitor account.
Optional Properties for Everpure (formerly Pure Storage) FlashArray Monitoring
The following properties are optional and can be set on the Everpure FlashArray resource or inherited from a parent group.
| Property | Default | Description |
|---|---|---|
purestorage.api.connectTimeout | 60000 | REST API connection timeout in milliseconds |
purestorage.api.socketTimeout | 60000 | REST API read/socket timeout in milliseconds |
purestorage.api.sessionCache | true | Enables collector-side session cookie cachingSet to false to bypass cached session reuse if session caching causes authentication issues |
Ports for Everpure (formerly Pure Storage) FlashArray Monitoring
You can use the following ports for monitoring:
| Protocol | Ports | Description |
| TCP | 443 | REST service access |
| UDP | 161 | SNMP (Optional) |
Troubleshooting
This monitoring package includes a Troubleshooting module that is visible only when a configuration or connectivity issue is detected. When an issue occurs, the module creates a troubleshooting instance with diagnostic information to help identify the cause.
Common issues include invalid credentials and unsupported or incompatible REST API versions.
LogicModules in Package
LogicMonitor’s package for Everpure (formerly Pure Storage FlashArray) contains the following LogicModules. Ensure all LogicModules are imported into your LogicMonitor platform.
Important: Everpure (formerly Pure Storage) modules retain their existing PureStorage module names and technical identifiers, including categories and properties, for compatibility.
| Name | Type | Description |
|---|---|---|
addCategory_PureStorage | PropertySource | Adds the PureStorage category to resources that return a Pure Storage login page. |
addERI_PureStorage | PropertySource | Sets Pure Storage external resource IDs for topology correlation. |
Volume Utilization | DataSource | Monitors Pure Storage volume capacity and utilization metrics using the REST API. |
Volume Performance (Older API versions) | DataSource | Monitors Pure Storage volume performance metrics via the REST API for arrays using older API versions. |
Volume Performance | DataSource | Monitors Pure Storage volume performance metrics via the REST API. |
Temperature Sensors | DataSource | Monitors Pure Storage temperature sensor status and readings via the REST API. |
PureStorage_ArrayInfo | PropertySource | Collects Pure Storage array inventory properties from the REST API. |
PureStorage_API_Versions | PropertySource | Discovers supported Pure Storage REST API versions and stores them as resource properties. |
PureStorage Troubleshooter | DataSource | Reports Pure Storage REST API authentication status when API version discovery has not completed. |
Drive Status | DataSource | Monitors Pure Storage drive bay health and status using the REST API. |
Component Status | DataSource | Monitors Pure Storage hardware component status using the REST API. |
Array Utilization | DataSource | Monitors Pure Storage array capacity and utilization metrics using the REST API. |
Array Performance SNMP | DataSource | Monitors Pure Storage array performance metrics using SNMP. |
Array Performance | DataSource | Monitors Pure Storage array performance metrics using the REST API. |
Array Controllers | DataSource | Monitors Pure Storage array controller status using the REST API. |
PureStorage_Topology | TopologySource | Generates Pure Storage topology relationships. |
When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations.
Recommendation: If necessary, adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.



