storage::purestorage::flasharray::v2::restapi::mode::arrays - extend perf counter

[rmorandell-pgum]

Community contributors

Description

Extend the existing performance counter with that ones:

https://support.purestorage.com/bundle/m_microsoft_platform_guide/page/Solutions/Microsoft_Platform_Guide/a_Windows_PowerShell/topics/concept/c_applies_to_166.html

• queue_usec_per_read_op (int) – The average time that a read I/O request spends in the array waiting to be served. Measured in microseconds.
• queue_usec_per_write_op (int) – The average time that a write I/O request spends in the array waiting to be served. Measured in microseconds.
• bytes_per_read (int) – The average I/O size per read. Measured in bytes.
• bytes_per_write (int) – The average I/O size per write. Measured in bytes.
• read_bytes_per_sec (int) – The number of bytes read per second.
• reads_per_sec (int) – The number of read requests processed per second.
• service_usec_per_read_op (int) – The average time required for the array to service a read request. Measured in microseconds.
• service_usec_per_write_op (int) – The average time required for the array to service a write request. Measured in microseconds.
• usec_per_read_op (int) – The average time it takes the array to process an I/O read request. Measured in microseconds. The average time does not include SAN time, queue time, or QoS rate limit time.
• usec_per_write_op (int) – The average time it takes the array to process an I/O write request. Measured in microseconds. The average time does not include SAN time, queue time, or QoS rate limit time.
• write_bytes_per_sec (int) – The number of bytes written per second.
• writes_per_sec (int) – The number of write requests processed per second.

Type of change

• Patch fixing an issue (non-breaking change)
• New functionality (non-breaking change)
• Functionality enhancement or optimization (non-breaking change)
• Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

test data send via private message

Checklist

• I have followed the coding style guidelines provided by Centreon
• I have commented my code, especially hard-to-understand areas of the PR.
• I have rebased my development branch on the base branch (develop).
• I have provide data or shown output displaying the result of this code in the plugin area concerned.