+1 for Opsview. I have a reasonable amount of experience with it of late, It ticks most of the boxes mentioned here. For those of you who aren't aware - it's basically Nagios on steroids. Full commercial support is available or there is a community edition with almost all of the features in the commercially supported version. It has a data warehouse built in, supports multiple distributed monitoring points, SNMP Traps can be handled via passive checks, a neat web interface, android client, built in reports and a REST API that works really well. The commercially supported version also integrates with RANCID, Jasper reports and has a service desk connector (integrates with RT and such). http://www.opsview.com/community/compare-opsview Oh they have a module for puppet too :) On 30 August 2011 22:28, Geraint Jones <geraint(a)c10kconsulting.com> wrote:
OpsView.
That is all.
From: Jonathan Brewer <jon.brewer(a)gmail.com> Date: Tue, 30 Aug 2011 22:18:02 +1200 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
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog