We've been using Cricket for a while and have been really happy with it. We use it for cpu, memory, throughput, etc, as well as for SLB stats from Cisco IOS (kinda messy, though). Setting up new new items to monitor is generally pretty easy, the SLB stats being the only exception I've run into. Alarms are also easy to set up and can be configured as persistent or non-persistent. Aggregation works pretty nicely, which allows you to combine all of your links into one aggregated bandwidth summary graph, for instance.
Recently, I started pulling SLA pages with Cricket, using the built-in http feature, and it does a pretty nice job, though I also use Smokeping for this, as it provides more detailed results. Hope this helps, Joe On Thu, 27 Mar 2003, Vicky Rode wrote: > Hi there, > > I would like to know what people are using and/or recommend for a front-end > (w/ rrdtool as a backend) which would address the following at minimum: > > -- fault-management (alerts, alarms...etc) > -- performance monitoring (throughput, utilization...etc) > > I'm looking at NMIS (http://www.sins.com.au/nmis/) but just wondering what > folks think of this front-end compared to others and their recommendation. > > > Any insight will be appreciated. > > > regards, > /vicky > > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Help mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/rrd-users > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi > -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
