Pure Storage MonitoringLast updated on 17 March, 2023
Pure Storage develops all-flash data storage hardware and software products. LogicMonitor offers a suite to monitor performance statistics for Pure Storage arrays.
As of September 2020, LogicMonitor’s Pure Storage package is compatible with Pure Storage devices exposing the Pure Storage REST API version 1 (1.5 and later); version 2.x is not currently supported. All LogicModules accessing the API will default to using the highest available version of the 1.x REST API.
- The LogicModules in this package use the Pure Storage REST API. Refer to their documentation here.
- Overall array performance statistics are extracted using SNMP. Configuring only SNMP requires the module:
You will need a new or existing user with read-only access to the device. Depending on your PureStorage configuration, this may be created locally on the device itself or externally through an Active Directory or LDAP integration.
Create an API Token for the account using the Purity GUI or the CLI.
- In the Purity GUI, go to System > Users > Create API Token
- On the CLI, run the command:
pureadmin create --api-token
Your token should look like:
|purestorage.apitoken.pass||Pure Storage API token|
Associate your PureStorage API Token with your device by adding it as a device property of the name purestorage.apitoken.pass. Refer to Pure Storage’s documentation for creating tokens here.
Enter the port(s) used by the technology suite.
|TCP||443||REST service access|
The following PropertySources must be installed for modules in this package to work:
This package contains a Troubleshooting module that should only be visible if there is a problem during setup. If there is a problem, the module should create a troubleshooting instance displaying problems.
Examples of setup issues include bad credentials or incompatible API versions (such as for older equipment).
LogicModules in Package
LogicMonitor’s package for Pure Storage contains the following LogicModules. Please ensure that all of these LogicModules are imported into your LogicMonitor platform.
|addCategory_PureStorage||PropertySource||Adds system.categories=PureStorage to devices that return a login page when queried.|
|addERI_PureStorage||PropertySource||Sets Pure Storage ERI and StorageNode ERT for topology mapping purposes.|
|Volume Utilization||DataSource||PureStorage Volume Utilization as provided by REST API. Some systems do not return shared_space.|
|Volume Performance (Older API versions)||DataSource||PureStorage Volume Performance as provided by REST API.|
|Volume Performance||DataSource||PureStorage Volume Performance as provided by REST API.|
|Temperature Sensors||DataSource||PureStorage Temperature Status as provided by REST API.|
|PureStorage_ArrayInfo||PropertySource||Kept separate from the basic addCategory_PureStorage PropertySource deliberately.|
|PureStorage_API_Versions||PropertySource||Kept separate from the basic addCategory_PureStorage PropertySource deliberately. Finds supported API versions – mostly for possible future reference if data outputs change or versions are removed.|
|PureStorage Troubleshooter||DataSource||Visible if there is a problem with setup.|
|Drive Status||DataSource||PureStorage Array Performance as provided by REST API. Some systems do not return a ‘degraded’ value.|
|Component Status||DataSource||PureStorage Component Status as provided by REST API.|
|Array Utilization||DataSource||PureStorage Array Utilization as provided by REST API. Parity will be NaN if API is v1.7 or below.|
|Array Performance SNMP||DataSource||PureStorage Array Performance via SNMP.|
|Array Performance||DataSource||PureStorage Array Performance as provided by REST API. san_usec_per_read_op, san_usec_per_write_op will be NaN if API is v1.9 or below.|
|Array Controllers||DataSource||PureStorage Array Controller status as provided by REST API.|
|PureStorage_Topology||TopologySource||Generate Pure Storage topologies.|
When setting static datapoint thresholds on the various metrics tracked by this package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to 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.