From owner-freebsd-isp Fri Dec 14 13:28:21 2001 Delivered-To: freebsd-isp@freebsd.org Received: from nts.umd.edu (nts.umd.edu [128.8.5.5]) by hub.freebsd.org (Postfix) with ESMTP id 0562F37B416 for ; Fri, 14 Dec 2001 13:28:16 -0800 (PST) Received: from localhost (missing@localhost) by nts.umd.edu (8.11.3/8.11.3) with ESMTP id fBELRwx08492; Fri, 14 Dec 2001 16:28:07 -0500 (EST) (envelope-from missing@nts.umd.edu) Date: Fri, 14 Dec 2001 16:27:57 -0500 (EST) From: Tony To: Stanley Hopcroft Cc: Subject: Re: network management In-Reply-To: <20011215081404.A388@IPAustralia.Gov.AU> Message-ID: <20011214162102.B5086-100000@nts.umd.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 15 Dec 2001, Stanley Hopcroft wrote: > Dear Ladies and Gentlemen, > > On Fri, Dec 14, 2001 at 02:49:50PM -0500, Christopher Meiklejohn wrote: > > I have had alot of success with MRTG and NOCOL. > You may want to look at Netsaint (http://www.Netsaint.ORG) rather than > NOCOL. But NetSaint is not advertised as an snmp monitor. http://www.netsaint.org/docs/0_0_6/about.html#whatis Also, from what I understand, Netcool can do application monitoring. > > AFAIK, Netsaint is > > . actively developed > > . easier to write service checks for > > . supports various approaches for remote and distributed monitoring > > . has a fair to good story for monitoring M$ boxen. > > . has I think better logging and availability reporting How does Netsaint scale ? I may just have to go check the source myself. -Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message