Current metricbeat module for vsphere uses the "quick stats" metrics available in the API objects for virtual machines, host information and so on. vsphere SDKs also expose a set of performance metrics that expose many more metrics. We could complete vsphere support with these metrics.
We could review if this would replace the current metricsets, and/or if this could be implemented as new metricsets.
Go library we are using includes an example to collect these metrics: https://github.com/vmware/govmomi/blob/master/performance/example_test.go, with this code metrics like these ones can be collected.
This would help on the following issues:
Current metricbeat module for vsphere uses the "quick stats" metrics available in the API objects for virtual machines, host information and so on. vsphere SDKs also expose a set of performance metrics that expose many more metrics. We could complete vsphere support with these metrics.
We could review if this would replace the current metricsets, and/or if this could be implemented as new metricsets.
Go library we are using includes an example to collect these metrics: https://github.com/vmware/govmomi/blob/master/performance/example_test.go, with this code metrics like these ones can be collected.
This would help on the following issues: