Adding Useful Vcenter Receiver VM Performace Metrics

[samiura]

Component(s)

receiver/vcenter

Describe the issue you're reporting

Component(s)

receiver/vcenter

Describe the issue you're reporting

There are various metrics that we don't currently capture or could capture at a higher level as mentioned on this issue before.

Adding these six additional metrics to the Vcenter receiver and by default they are disabled. These six virtual machines related performance metrics are very useful for monitoring any Vcenter/ESXi server.

1. vcenter.vm.cpu.idle.time
2. vcenter.vm.cpu.wait.time
3. vcenter.vm.cpu.ready.time
4. vcenter.vm.cpu.latency.avg
5. vcenter.vm.network.multicast.packet.rate
6. vcenter.vm.network.broadcast.packet.rate

[samiura]

Please note I have an PR ready for this issue already here, so no need for someone to work on this at all.

[github-actions]

Pinging code owners for receiver/vcenter: @schmikei @StefanKurek. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[crobert-1]

Removing needs triage as a code owner has approved the PR implementing this change.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/vcenterreceiver: @schmikei @StefanKurek

See Adding Labels via Comments if you do not have permissions to add labels yourself.