> Friends from university days asked me an intriguing question the other day.
>
> How would you configure either Nagios or Zabbix to monitor how much data
> has flowed through a particular Ethernet interface for, say, the past 31
> days?
>
> I guess the idea is to set an alarm if they start to approach 85% (or
> whatever number) of that threshold to avoid need to pay excess bandwidth
> charges.
>
> I assist, free of charge, on my own time as they provide a valuable
> service free to the community. And, well, they're good guys, too. :)
>
> But how to do that? I haven't looked closely yet but still mulling it over.
>
> The standard bandwidth monitoring plugins in both monitoring systems
> appears to be a snapshot / moment-in-time, e.g. xx Mbps, rather than a
> total byte count over x days.
>
> Total byte count over x days also implies need to track state and counts...
>
> SNMP is a logical approach but the major flaw is that when snmpd is
> restarted (whether by reboot or otherwise), interface counters are reset.
>
> Any easy way to do that, or are these folks looking at a more involved
> solution of some sort?
>
> Any comments (snarky or otherwise :-) ) immensely appreciated!
>
> -Dan
>
> P.S. I'm very familiar with writing Nagios plugins, mostly in sh but
> sometimes perl. Zabbix, not as familiar, but have set it up before.
>
how about sflow for that task? sflow/netflow is really good about 
collecting aggregate data over time. Unfortunately, most of the sflow 
management platforms out there are Windows, but ManageEngine makes one 
(java + mysql + snmp) that works under Linux that is pretty good. We 
bought a license for it. Also Wireshark is another that appears to 
support it, but I didn't check to see what extent. Netflow enjoys a bit 
more wider support being Cisco proprietary and has a bunch of OSS tools 
for collecting it.

_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to