This issue is about creating a collector for ONTAP objects that includes a statistics or metric field in the ONTAP response. This collector is distinct from the ZapiPerf and RestPerf collectors since the shape of the ONTAP response for statistics and metric is different from the ONTAP responses for ZapiPerf and RestPerf.
In general, the statistics and metric fields include performance metrics for IOPS, latency, and throughput. The statistics metrics are raw performance counters, while the metric counters are samples over one of the predefined ranges (15 seconds, four minutes, five minutes, 30 minutes, two hours, one day).
The statistics field is more general and likely covers all of Harvest's use cases. If that's true, we may only support the statistics field and ignore the metric field. The metric field is difficult to make work with Prometheus since Prometheus controls the timestamp used to stamp the metrics, not Harvest.
Background
The statistics and metric counters are aggregated across all nodes in the cluster. These counters have existed since ONTAP 9.6, and as of ONTAP 9.15.1, the statistics field is available for the following 25 objects. The /application/applications endpoint is different from the other endpoints since /application/applications's response includes statistics but no metric, includes additional fields beyond IOPS, latency, and throughput, and also uses a different naming convention.
This issue is about creating a collector for ONTAP objects that includes a
statistics
ormetric
field in the ONTAP response. This collector is distinct from theZapiPerf
andRestPerf
collectors since the shape of the ONTAP response forstatistics
andmetric
is different from the ONTAP responses forZapiPerf
andRestPerf
.In general, the
statistics
andmetric
fields include performance metrics for IOPS, latency, and throughput. Thestatistics
metrics are raw performance counters, while themetric
counters are samples over one of the predefined ranges (15 seconds, four minutes, five minutes, 30 minutes, two hours, one day).The
statistics
field is more general and likely covers all of Harvest's use cases. If that's true, we may only support thestatistics
field and ignore themetric
field. Themetric
field is difficult to make work with Prometheus since Prometheus controls the timestamp used to stamp the metrics, not Harvest.Background
The
statistics
andmetric
counters are aggregated across all nodes in the cluster. These counters have existed since ONTAP 9.6, and as of ONTAP 9.15.1, thestatistics
field is available for the following 25 objects. The/application/applications
endpoint is different from the other endpoints since/application/applications
's response includesstatistics
but nometric
, includes additional fields beyond IOPS, latency, and throughput, and also uses a different naming convention.Status field
The collector needs to handle all
status
enums:Examples
Alternative names