Zabbix monitor whole ethernet port usage

[alexc]

As I try to gather PVE node stats with Zabbix I found I can not get real port usage for physical port that faces the WAN link. Vmbr0 stats seems to show only own node usage, but I need whole link usage (own node plus all of VMs usage).

Silly question I know but can’t fond a way. Vmbr0 vs switch port usages are completely different si seems like I miss something?

 

[wolfgang]

Hi,

If you like the monitor every VM/CT you have to monitor the tap/veth devices.w

 

[alexc]

Sorry, I must be misexpress my problem. I do not need to monitor each VM interface. Instead, I messed up with only total "uplink" traffic graph. So to say, I don't care for PVE host internal traffic, but want to know how much external (= WAN) traffic is used and may this bandwidth be limited by external infrastructure.

You see, I used to consider vmbr0 as a uplink interface since this is something we add to every VM. But as I can see, vmbr0 is not reflecting "sum" of VM traffic but instead this is some "internal" interface, and I need to monitor what - "eth0" / "eno1"? or I need to get all VMs interfaces and sum its bandwidth?

So the question is "which interface should I monitor to see total (sum) of external (WAN) traffic (all VMs/CTs and PVE itself)?"

 

[wolfgang]

You can monitor for all outgoing traffic the "bridge-ports".
On this device is no internal vmbr traffic.
On the vmbr is also internal VM/CT to VM/CT traffic included.

 

[alexc]

From what I can see on one of my hosts, there are no such ports as "bridge-ports". May I mistook your naming and it is there, named differently?

Here is what I have (a bit filtered to hide IPs and have it shorter):

root@host-one:~# ifconfig  | grep mtu
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
eno2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
eno2.10: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
eno2.11: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
eno2.12: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
fwbr120i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
fwln120i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
fwpr120p0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
tap120i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
tap120i1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
tap150i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
tap712i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
tap714i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
tap715i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
vmbr1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
vmbr1v10: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
vmbr1v11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
vmbr1v12: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

 

[wolfgang]

the bridge-port is defined in the network config at
/etc/network/interfaces at the vmbr0 section