-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/vcenter] Add support for per network/nic metrics #31218
Labels
Comments
wally007
added
enhancement
New feature or request
needs triage
New item requiring triage
labels
Feb 13, 2024
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Any thoughts on this @schmikei? |
This was referenced Feb 20, 2024
This was referenced Feb 27, 2024
This was referenced Mar 5, 2024
This was referenced Mar 19, 2024
I am sorry for the duplicate issue. I will close this now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component(s)
receiver/vcenter
Is your feature request related to a problem? Please describe.
Currently, the vCenter network metrics are exported per host. Most, if not all ESXi hosts have several nics/network assigned. In my case, I'm administering hosts with 12+ networks. It is impossible to monitor network utilization of ESXi hosts.
Describe the solution you'd like
It would be useful if network metrics were NOT aggregated per host but exported per host + nic/network in order to be able to effectively monitor for network errors and network congestion.
(metrics like network bandwidth, network errors, packets etc ..)
Describe alternatives you've considered
Currently we use telegraf to monitor vsphere environment but we'd like to move to OpenTelemetry. Telegraf exports network metrics per vnic (which makes it easy to map it to the nic/network)
Additional context
No response
The text was updated successfully, but these errors were encountered: