[9.0](backport #44205) capture extra vsphere metrics (cpu %, disk average, disk rate, disk n… #44496
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…umber, memory usage %)
Proposed commit message
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Using

vcsim
simulation of vSphere API not all metrics were available to check (it appears that vcsim doesn't generate disk usage metrics).So only 2 of the new metrics were generated by vsim (
cpu.percent
andmemory.percent
):However when I tried commenting out the check if a metric is in list of "available" metrics in the code (line 70 in metricbeat/module/vsphere/client/performance.go) it showed more metrics:

So only
disk.numberWrite
anddisk.numberRead
I wasn't able to test at all.Logs
This is an automatic backport of pull request #44205 done by [Mergify](https://mergify.com).