-
Notifications
You must be signed in to change notification settings - Fork 710
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
Collector net don't show nic name as expected #1835
Comments
It seems like the different version of Windows APIs do sanitize name in different ways. While on 0.28.0 space also replaced with an However, I agree that the nic label in |
Thanks! And if it's possible to add the “friendly_name” in all metrics containing “nic=” ? It would help to easily identify a NIC. |
Due my understanding how prometheus, I can't recommend that. The general idea is to have a info metric (I do the same for process and services, too) and then using promql capabilities to join labels. Something like this may work:
and should result into the expected behavior. Ref: https://ypereirareis.github.io/blog/2020/02/21/how-to-join-prometheus-metrics-by-label-with-promql/ |
Got it! The PromQL query you provided works. The nic name on all collectors must be the same to match. |
Yeah, that what I mean in my first response.
|
Current Behavior
I was trying the new version of windows_exporter (0.30.0), and I noticed that the 'net' collector was not returning the correct information.
0.28.1
TYPE windows_net_bytes_sent_total counter
windows_net_bytes_sent_total{nic="vmxnet3_Ethernet_Adapter"} 2.532306e+06
windows_net_bytes_sent_total{nic="vmxnet3_Ethernet_Adapter__2"} 3.2228776e+09
0.30.0
TYPE windows_net_bytes_sent_total counter
windows_net_bytes_sent_total{nic="vmxnet3 Ethernet Adapter"} 1.8390094e+07
windows_net_bytes_sent_total{nic="vmxnet3 Ethernet Adapter _2"} 1.5852902351e+10
NIC names are spelled differently between 0.28.1 and 0.30.0
and also a different spelling in the metrics windows_net_nic_address_info
TYPE windows_net_nic_address_info gauge
windows_net_nic_address_info{address="x.x.x.x",family="ipv4",friendly_name="xxx",nic="vmxnet3 Ethernet Adapter"} 1
windows_net_nic_address_info{address="x.x.x.x",family="ipv4",friendly_name="xxx",nic="vmxnet3 Ethernet Adapter #2"} 1
Expected Behavior
is it possible to normalize all this and also it would be interesting to have the “friendly_name” in all metrics containing “nic=”
Steps To Reproduce
Environment
windows_exporter logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: