I recently did an evaluation (and sample deployment) of both MRTG and
Cricket. Cricket was by far the superior choice.
It's easier manage large cricket configurations than large MRTG
configurations. It allows you to collect many different SNMP (and also
non-snmp) statistics, and to view these collected statistics in multiple
ways for each target. It's faster at data collection than MRTG, it uses
less disk space for data storage/display storage than MRTG, and it supports
parallelization of data collection.
The down side is that the configuration tree is a bit harder to wrap your
mind around than MRTG's flat file, but once you get the hang of it you'll
wonder why more programs don't use it's approach.
- Jeff Younker - [EMAIL PROTECTED] - These are my opinions, not MDL's -
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
