we are far from 1000+ nodes in the moment but i was there already. I
currently run stats gathering separate from notification/alerting. for
the stats gathering i use a combination of collectd and graphite. the
notification bit is home grown and would currently not scale to your
needs.
a really good article about monitoring is this one from the MT guys:
http://weblog.mediatemple.net/2011/04/07/getting-more-signal-from-your-noise...
cheers
lenz
On Wed, Aug 31, 2011 at 11:49 AM, Cameron
I’m also in a similar position.
I’m currently using Nagios + a large amount of customisation but I have a few requirements coming up that Nagios won’t be able to do. OpenNMS is looking like the likely candidate but I also want to evaluate Zenoss and Zabbix. I hadn’t seen them mentioned here yet so I thought I’d throw the names out and see if anyone has tried either of them at all. Scaling is the issue I guess, Nagios just does it so well.
Cameron
________________________________
From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Jonathan Brewer Sent: Tuesday, 30 August 2011 8:18 PM
To: nznog(a)list.waikato.ac.nz Subject: [nznog] Nagios vs. OpenNMS vs. SomethingElse
Hi Folks,
If you had it all to do over again, what would you use for network monitoring: Nagios, OpenNMS, or something else entirely?
I care about availaility, latency, loss, jitter, and trap handling for interface up/down, loss of power, etc. Sensible behavior in situations where parent routers/links are flapping is also important.
I would very much appreciate input from folks monitoring 1000+ network elements.
Cheers,
Jon
------------------------------------- +64 27 502 8230 http://about.me/jonbrewer -------------------------------------
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
-- twitter: @norbu09 current project: iWantMyName.com