On Fri, 22 Mar 2013, Edward Ned Harvey (lopser) wrote:

I've used zenoss before.  Didn't like it.  We had problems with the accuracy of metrics 
(I think it buffer overflowed or something, getting disk usage on a several TB volume, 
reported things like -50% full) ... even though "technically" it could allow 
you to create custom metrics via ssh and so forth, it was confusing, never got that 
working, etc.

I haven't used any of these others.

Looking at the nagios site, it looks like, you're supposed to install it on the 
server you monitor.  Installing httpd, mysql, configuring selinux, etc.  Which 
is not what I want.

I want to install a centralized monitoring / alerting system, and deploy a tiny 
little plugin (or something) to each of the systems to be monitored.  The 
production systems already run apache, mysql, etc, and I don't want any 
dependencies on any installation packages to conflict or cause any disruption 
to existing production services.  If I need to configure httpd on the system to 
be monitored, it's a nonstarter.

I primarily care about linux systems (but other OSes are nice to support too).  
Want alerts, both predictive and reactionary (notify me if a system is down, 
but also notify me when disk usage is over 90% or the CPU stays over 95% for 10 
minutes, or the system begins thrashing swap, etc, so I can hopefully avoid 
system down.)  etc.

Thanks for suggestions.


If you want a simple to install and easy to manage Nagios based solution, look at Opsview Core. For your client systems, install the opsview-client (NRPE) and you're good to go.

http://www.opsview.com/technology/downloads/opsview-core

-phillip
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/

Reply via email to