-
Change Request
-
Resolution: Unresolved
-
Trivial
-
None
-
1.8.20, 2.0.10, 2.2.3
-
all systems supporting net.if.discovery
I have linux servers tha are running many virtual machines. On these systems I have 4 physical interfaces, 20 vlan interfaces (for access to different networks), 20 bridge interfaces (one for each vlan) and 10 vnet interfaces (1 for every virtual machine). When I use default net.if.discovery i have too many items and I don't want them. I need statistics only for physical interfaces. it would be nice to add field #IFTYPE get would look like this:
[root@zabbix zabbix]# zabbix_get -s client -k net.if.discovery { "data":[ { "{#IFNAME}":"lo", "{#IFTYPE}":"localhost" }, { "{#IFNAME}":"eth0", "{#IFTYPE}":"physical"}, { "{#IFNAME}":"eth1", "{#IFTYPE}":"physical"}, { "{#IFNAME}":"eth2", "{#IFTYPE}":"physical"}, { "{#IFNAME}":"eth3", "{#IFTYPE}":"physical"}, { "{#IFNAME}":"eth0.200", "{#IFTYPE}":"vlan"}, { "{#IFNAME}":"brbackbone", "{#IFTYPE}":"bridge"}]}
filters for discovery could be adjusted by MACROs same as it is for vfs.fs.discovery.
- related to
-
ZBXNEXT-7502 Change net.if.discovery and add new keys
-
- Open
-
-
ZBXNEXT-5367 Extend net.if metrics on Linux using sysfs net
-
- Open
-
-
ZBX-21697 Linux reports wrong speed for vnet devices (KVM guests)
-
- Confirmed
-
-
ZBX-24442 zabbix agent overwhelms its log file about virtual network interfaces
-
- Confirmed
-
-
ZBX-20869 Item: vfs.file.contents["/sys/class/net/IF/speed"] unsupported on some systems
-
- Confirmed
-
-
ZBX-24057 Reporting speed for wlanX fails
-
- Confirmed
-
-
ZBX-25960 Interface speeds for down interface not caught by vfs.file.contents["/sys/class/net/{#IFNAME}/speed"]
-
- Confirmed
-