[128903] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Monitoring Tools

daemon@ATHENA.MIT.EDU (Mike Gatti)
Thu Aug 19 15:59:22 2010

From: Mike Gatti <ekim.ittag@gmail.com>
In-Reply-To: <02a501cb3fd1$2cb70de0$862529a0$@net>
Date: Thu, 19 Aug 2010 15:59:09 -0400
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Looking at ZenOSS to compliment our OpenView NNM system.=20
So far has been pretty simple to get up and running and the=20
support community is pretty responsive to questions.

We have cacti in our environment and it works great for pulling=20
bandwidth, CPU, interface errors, mem utilization. the reportit plugin
in particular is great for reporting bandwidth utilization for business =
hours.=20


--
Mike



On Aug 19, 2010, at 3:03 PM, Scott Berkman wrote:

> The last time I looked, my main issue with Zabbix was that it required =
(or
> greatly preferred) their proprietary agent on every host.  This may =
have
> changed.
>=20
> 	-Scott
>=20
> -----Original Message-----
> From: Nathan Eisenberg [mailto:nathan@atlasnetworks.us]=20
> Sent: Thursday, August 19, 2010 2:53 PM
> To: nanog@nanog.org
> Subject: RE: Monitoring Tools
>=20
>> Am looking for an opensource network monitoring tool with ability to
> create
>> different views for different users.
>>=20
>> Regards,Jacob
>>=20
>=20
> Just to add another opinion to the pot, I've used zabbix in several =
large
> environments, and I like it a lot.  The developer team is decently =
sized,
> and very responsive to requests and feedback (they operate a =
commercial
> 'support' model for the platform, so working on the system is =
literally
> their day job - as George pointed out, this is often a problem).
>=20
> Zabbix also supports distributed monitoring, which is very handy for =
scaling
> or for monitoring multiple locations without dealing with VPNS and the =
like
> (or if you have places you need to monitor behind NATs!).  Its major
> weakness at the moment is the weak support for SNMP traps (works great =
in
> polling mode, though), so you will want a separate simple system for
> catching traps.  In my opinion, that's just fine, because
> statistics/trending/basic resource alerting/etc are best kept separate =
from
> things like "OMG one of my powersupplies is dead!!11one".
>=20
> Also supports IPMI, which is nice if you have IPMI deployed.  :-)
>=20
> Best Regards,
> Nathan Eisenberg
>=20
>=20
>=20
>=20

=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D
Michael Gatti =20
cell.703.347.4412
ekim.ittag@gmail.com
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D





home help back first fref pref prev next nref lref last post