Too much coffee and RRDTool/Cricket/MRTG


Subject: Too much coffee and RRDTool/Cricket/MRTG
From: Christopher E. Brown (cbrown@woods.net)
Date: Sun Apr 20 2003 - 13:05:55 AKDT


How can there be such a thing as too much coffee?

The saga of the stats aside, MRTG and Cricket are both great packages.

MRTG is simple and it is the only standby.

Cricket offers some neat stuff, but it is a more complex package. The
configuration tree offers alot of flexibility, very useful with large
networks, and multiple admins handling different parts of it. But, it
makes it a fair bit more difficult to configure.

If you want to graph the in and the out, MRTG is lightweight, easy to
configure and just works.

If you want to track and graph the in and the out, and say transmit
and receive errors (or any other useful/related data) on the same
graph, or you have several hundred devices/ports Cricket starts
looking *real* good.

Also, SUM data (say you need to report the aggregate data flow
into/out of a facility over multiple network links/routers) does not
require nearly the level of hackage and workarounds with Cricket as it
does with MRTG.

-- 
I route, therefore you are.

--------- To unsubscribe, send email to <aklug-request@aklug.org> with 'unsubscribe' in the message body.



This archive was generated by hypermail 2a23 : Sun Apr 20 2003 - 13:04:33 AKDT