Custom maps edge only accepting Egress from interface description

[Jock_McTavish]

Possibly a bug here but before I submit on github I thought I’d check I wasn’t being stupid first.
So according to convention and libreNMS docs, I can add [ingress/egress] to an interface name.

However, when adding Edge links to custom maps, it appears that the ingress limit is being applied to both directions when calculating utilisation.

For example, here I have Port:Tranzit-core - vlan415-snowden-5x[70M/230M]. It’s showing the correct Mbps and direction for the traffic flowing through the Edge (link) but the percentage utilisation for both directions appears to be based on just the ingress (70M).

[laf]

The code suggests that’s it not using the same port direction and this is the first report so I’m not sure it’s a bug.

Are you using port parsing and if so, what’s the value of port_descr_speed from the ports table for the port in question?

[Jock_McTavish]

Hi, I’ve not setup any configuration for port parsing. The only thing I’ve done is add the interface ingress/egress.

mysql -u librenms -p librenms -e “SELECT port_id, ifAlias, port_descr_speed FROM ports WHERE port_id = 246894;”
Enter password:
±--------±-----------------------------±-----------------+
| port_id | ifAlias | port_descr_speed |
±--------±-----------------------------±-----------------+
| 246894 | vlan415-snowden-5X[70M/230M] | 70M/230M |
±--------±-----------------------------±-----------------+

[laf]

So between those two devices, you’ll have two ports, one for each device. You’ve obviously picked one port from one device, can you edit the edge and choose the other port from the other device and see.

What I think is happening is that the direction of the traffic is flowing in the opposite direction of your port_descr_speed. The % calculations indicate that, 2.8% =0.028 230M and 149.59% =1.496 70M

[murrant]

FYI, it is actually egress/ingress, which seems kind of backwards

[Jock_McTavish]

Thanks. Tested and its now spot on. I should have RTFM. See my first post about being stupid. And yes, [egress/ingress] is the complete opposite of other network monitoring tools. Custom interface parser might be the go…

Interface Description Parsing - LibreNMS Docs

[murrant]

I just updated the docs it wasn’t there before to give your self a little slack. It might have been able to be inferred, but it wasn’t explicit.