Not sure if still relevant seeing how old the ticket is, but:

High traffic: already being monitored by LibreNMS

Low traffic: hard to monitor and maintain as the baseline would need to either be manually set, or have something that analyses the historical values to set it automatically

No traffic: Can be easily monitored using LibreNMS
For that we would need to:

1. Remove (or fix) the 2 interfaces that are tagged with Transit/Peering but never saw traffic
   • cr1-ulsfo.wikimedia.org:xe-0/0/3.98
   • xe-5/2/3.40
2. Tag the OOB interfaces with something different than Transit (could be Transit-OOB, Uplink-OOB, etc..), as they are not "revenue" ports, and have significantly less bandwidth than standard uplinks
3. Add LibreNMS alert to match a ifOutOctets_rate of 5M or something small enough to alert if there is only control traffic on the interface and no more proper traffic

@faidon does that sound reasonable to you?

As we have some link with 0.2% of outbound traffic, I added a LibreNMS rule to alert if any traffic or peering link drops under 0.1% of outbound traffic.

Will monitor and update if needed.