-
Incident report
-
Resolution: Unresolved
-
Major
-
None
-
6.2.3
-
None
-
RHEL 7,8,9
Steps to reproduce:
- Use the latest "Linux by zabbix agent (active)" template
- Have kvm based vms running on the host
- Have vnet interfaces discovered
- Verify the link speed
Result:
Kernel always reports link speed of 10mbit for any vnet* devices related to kvm virtual machines, so the speed related trigger is fired.
Someone reported this on the forum:
https://www.zabbix.com/forum/zabbix-help/359479-centos-kvm-incorrect-speed-for-vnet-interfaces
See:
https://access.redhat.com/solutions/65061
Quote: "vnet interfaces are tap devices. The 10Mbps is just a cosmetic figure in a tap device's virtual firmware. This speed has no bearing on the speed of a guest's virtual device whatsoever."
Expected:
vnet devices should likely be excluded in the default regex for {$NET.IF.IFNAME.NOT_MATCHES}
- related to
-
ZBXNEXT-2286 net.if.discovery filtration
-
- Open
-
-
ZBXNEXT-7502 Change net.if.discovery and add new keys
-
- Open
-
-
ZBXNEXT-5367 Extend net.if metrics on Linux using sysfs net
-
- Open
-
-
ZBX-20869 Item: vfs.file.contents["/sys/class/net/IF/speed"] unsupported on some systems
-
- Confirmed
-
-
ZBX-25960 Interface speeds for down interface not caught by vfs.file.contents["/sys/class/net/{#IFNAME}/speed"]
-
- Confirmed
-
-
ZBXNEXT-10156 Add interface speed overrides for Linux by Prom and SNMP templates
-
- READY TO DEVELOP
-
-
ZBX-24442 zabbix agent overwhelms its log file about virtual network interfaces
-
- Confirmed
-
-
ZBX-24057 Reporting speed for wlanX fails
-
- Confirmed
-