My vote would be for the method that uses the least amount of resources (within reason). If the data is available using existing interfaces and does not require additional software (like mrtg), it's goodness (as long as it's accurate). I have no reason to think that ifconfig wouldn't be accurate.
A separate graph per interface works for me (that's the way the mrtg implementation does it).
The worst thing for a monitor to do is to become a performance problem.
Henrik Stoerner wrote:
On Thu, Nov 10, 2005 at 06:46:49AM -0600, Rich Smrcina wrote:
Jesper Johnson wrote:
I'm looking for a way to create graphs for hobbit on Linux to monitor network bandwidth usage, separately on each interface (eth0,eth1). The
There is a very well described MRTG interface for Hobbit. I just implemented it at a customer site and it works as advertised. The URL is in the help.
MRTG would indeed solve this problem.
But it might still make some sense to have the Linux hobbitclient collect the data from /sbin/ifconfig. It does have byte counters:
eth0 Link encap:Ethernet HWaddr 00:0E:A6:CE:D6:85 inet addr:172.16.10.100 Bcast:172.16.10.255 Mask:255.255.255.0
inet6 addr: fe80::20e:a6ff:fece:d685/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7935102 errors:0 dropped:0 overruns:0 frame:0
TX packets:7943900 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 RX bytes:2210282597 (2.0 GiB) TX bytes:2268014990 (2.1 GiB)
Interrupt:17
I dont think Hobbit should use these to populate the tcpOutDataBytes and
tcpInInorderBytes fields in the netstat rrd - the ifconfig counters are
per network interface, where the rest of the netstat data are global
counters.
But perhaps there should be a completely separate set of RRD files, with one graph per network interface ?
Regards,
Henrik
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (XXX)XXX-XXXX
Ans Service: (360)715-2467
user-61add9955ef9@xymon.invalid
Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006