[CentOS] Service monitoring/"Monit"?

Fri Jun 11 11:07:18 UTC 2010
Toralf Lund <toralf.lund at pgs.com>

Geoff Galitz wrote:
>> I think you are missing my point. This is precisely what I do not want
>> to do. The last bit here, I mean - i.e. I'm asking for a way to set up
>> so the "rename /etc/monit.d/sshd.conf to something different" step won't
>> be necessary.
> Depending on how much effort you are willing to put into this, you can get
> nagios to do this.  There are two options:
Hmmm... I've used Nagios before, but it must be 10 years ago now, so 
probably I'd have to re-learn it. But I'm sure it could be done.

I have a feeling that introducing nagios monitoring is a little too 
involved, though. I want to distribute the setup to external systems, so 
ideally there should be one "monitoring" package install and a simple 
"enable" command at the most, in addition to installation of the actual 

rpm -Uvh monit-<version>.rpm
chkconfig monit on

Is really quite ideal, except for the fact that it only nearly gives me 
what I want :-(

But thanks anyway,

- Toralf

> 1) Create a custom plugin that checks "service [app] status" or directly
> check the pid file and pgrep/grep for the app.  
> 2) Write a small script that you stick into the service init script that
> tells nagios to start or stop monitoring a service.  I used perl and LWP to
> do something very similar but you can probably find another CPAN module or
> something similar to act as interface to nagios.
> If you are comfortable with scripting and nagios you can bang out a solution
> in an afternoon.  Option 1 you can probably do in less than an hour and is
> probably better for you.  
> ---------------------------------
> Geoff Galitz
> Blankenheim NRW, Germany
> http://www.galitz.org/
> http://german-way.com/blog/
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos

This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.