-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harvest should create a KeyPerf
collector for ONTAP REST performance counters
#3008
Comments
|
KeyPerfMetrics
collector for ONTAP REST performance countersKeyPerf
collector for ONTAP REST performance counters
moving remaining work to next release |
Below dashboards can be excluded from KeyPerf tagging cmode/external_service_op.json |
Dashboards will be handled in a separate PR. Closing |
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
curl -k 'https://10.193.48.154/api/cluster?fields=statistics'
curl -k 'https://10.193.48.154/api/application/applications?fields=statistics'
Alternative names
The text was updated successfully, but these errors were encountered: