Sorry for the top post.
Nagios can start very simple, but has the ability to end up very complex.
It's configs take a modular approach, you have monitors, monitors belong in groups, groups have operators/administrators, etc.
My big problem with nagios is when I used it last it didn't keep monitor history which makes trending impossible.
I eventually went with ipmonitor from solarwinds which has a nice web interface, all the reporting you may want and works pretty much like nagios does, but through a web interface. Very reasonable pricing too.
Of course I believe it only runs on windows, but it runs very nicely as a VM guest.
-Ross
----- Original Message ----- From: centos-bounces@centos.org centos-bounces@centos.org To: CentOS mailing list centos@centos.org Sent: Tue May 13 07:34:50 2008 Subject: Re: [CentOS] Somewhat OT:
2008/5/13 Kai Schaetzl maillists@conactive.com:
Sergio Belkin wrote on Mon, 12 May 2008 23:07:20 -0300:
[CentOS] Somewhat OT:
even then please write a senseful subject next time!
Kai
-- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
Yes, you're roght Kai, I don't know how I could write such a stupid subject, but it was too late yersterday, and I was writing with a little part of my brain working :)
Even so, thanks for your comments, I'd like more experiences about monitoring systems. Again of topic, I want to avoid Nagios because it looks like over complex but if someone has an actual experience demostrating the opposite, I'd be glad to hear.
Thanks in advance
Ross S. W. Walker wrote:
Sorry for the top post.
Nagios can start very simple, but has the ability to end up very complex.
Network management is never simple. I'd say OpenNMS is somewhat the opposite in that the initial install can be somewhat complicated (although much less so now that they include the Sun jvm in their packaging), but it is designed to scale to large networks without a lot of additional work.
Ross S. W. Walker wrote:
Nagios can start very simple, but has the ability to end up very complex.
It's configs take a modular approach, you have monitors, monitors belong in groups, groups have operators/administrators, etc.
We just finished setting up Nagios at our office. It's not that bad once you break things out to sensible filenames instead of using one big config file. We stripped it down to just the essentials and are slowly building out our configuration to monitor additional services and hosts.
The other trick that we use is FSVS, which means that we have very good records as to what configuration file changes we made on the server. (FSVS is a front-end for storing stuff like /etc in a SVN repository.) It's extremely useful to be able to log configuration changes, browse past changes, do diffs on the files, etc.
-
Les Mikesell -
Ralph Angenendt -
Ross S. W. Walker -
Thomas Harold