Pure Arrays Test
Using this test, administrators can figure out how well the FlashArray processes the I/O requests and detect delay encountered during processing the I/O requests. In addition, this test also reports the data utilization for performing read/write operations on the FlashArray. Using the metrics reported by this test, administrators can take remedial measures to keep a check on the irregularities, if any.
Target of the test : Pure Storage FlashArray
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the target FlashArray being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The IP address of the host for which this test is to be configured. |
Port |
The port at which the device listens. By default, this will be NULL. |
API Token |
The eG agent collects the required metrics from the Pure Storage Flash Array by executing API commands using Pure Storage REST API on the FlashArray and pulls out critical metrics. In order to collect metrics, the eG agent should be provided with a valid API token. To know how to determine the API token, refer to Pre-requisites for Monitoring the Pure Storage FlashArray. Specify the determined API token in the API Token text box. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Read bandwidth |
Indicates the amount of data utilized for performing read operations on this FlashArray per second. |
MB/Sec |
A consistent decrease in the value of these measures indicates an I/O processing bottleneck.
|
Write bandwidth |
Indicates the amount of data utilized for performing write operations on this FlashArray per second. |
MB/Sec |
|
Average bandwidth |
Indicates the average amount of data utilized for performing I/O operations on this FlashArray per second. |
MB/Sec |
|
Read IOPS |
Indicates the number of read operations performed on this FlashArray per second. |
IOPS |
A consistent decrease in the value of these measures indicates an I/O processing bottleneck.
|
Write IOPS |
Indicates the number of write operations performed on this FlashArray per second. |
IOPS |
|
Average IOPS |
Indicates the average number of I/O operations performed on this FlashArray per second. |
IOPS |
|
Read latency |
Indicates the time taken to process the read operations during the last measurement period. |
Milliseconds |
Very high values for these measures are indicative of the existence of road-blocks to rapid reading/writing by the FlashArray.
|
Write latency |
Indicates the time taken to process the write operations during the last measurement period. |
Milliseconds |
|
Average latency |
Indicates the average time taken to process the I/O operations during the last measurement period. |
Milliseconds |
Ideally, the value of this measure should be very low. A high value or a steady increase in this value could indicate an I/O processing bottleneck on the array. In such a case, compare the value of the Read latency and Write latency measures to figure out where the slowness is worst - when processing read requests? or write requests? |
Queue depth |
Indicates the number of IO requests in the queue. |
Number |
A consistent increase in this value indicates a potential processing bottleneck with the FlashArray. |