-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Adding Useful Vcenter Receiver VM Performace Metrics #37488
Comments
Please note I have an PR ready for this issue already here, so no need for someone to work on this at all. |
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. |
Removing |
…37489) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR adds the following VM performance metrics for vcenter. 1. `vcenter.vm.cpu.time` 2. `vcenter.vm.network.multicast.packet.rate` 3. `vcenter.vm.network.broadcast.packet.rate` More information on these metrics can be found [here](https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.metrics.doc/GUID-41603CD6-453B-4E26-A237-34E733BAB00C.html). and also succinctly described [here](https://www.servicenow.com/docs/bundle/xanadu-it-operations-management/page/product/agent-client-collector/reference/vsphere-metrics.html) <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #37488 <!--Describe what testing was performed and which tests were added.--> #### Testing The metrics were scraped from a test vCenter environment, and golden test files were updated accordingly to reflect the addition of the metric. <!--Describe the documentation added.--> #### Documentation Documentation was updated according to the metadata.yaml <img width="1776" alt="evidence1" src="https://github.com/user-attachments/assets/662d6ff5-dda5-4e56-b124-5b401992871a" /> <img width="650" alt="Screenshot 2025-01-29 at 10 48 33 AM" src="https://github.com/user-attachments/assets/c421ed17-d718-4f78-b5d1-4b96627d7584" /> <img width="125" alt="Screenshot 2025-01-29 at 10 53 54 AM" src="https://github.com/user-attachments/assets/12317bf0-d767-4d6d-ad2f-0daf07c18555" /> <img width="933" alt="Screenshot 2025-01-29 at 10 54 11 AM" src="https://github.com/user-attachments/assets/331a31fb-0574-4465-8fc5-240be40e2684" /> Signed-off-by: Samiur Arif <[email protected]>
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.
vcenter.vm.cpu.idle.time
vcenter.vm.cpu.wait.time
vcenter.vm.cpu.ready.time
vcenter.vm.cpu.latency.avg
vcenter.vm.network.multicast.packet.rate
vcenter.vm.network.broadcast.packet.rate
The text was updated successfully, but these errors were encountered: