Single check script to monitor multiple processes

[Showkilr]

I currently have a script that performs this exact function. and keeps
the output from being larger than the buffer for being called via nrpe..

Its a rather simple perl script and only requires a simple config file
to allow one to specify what processes to monitor.

Showkilr

On Fri, 2003-05-02 at 12:03, Carroll, Jim P [Contractor] wrote:
> It's not currently being done.  Well, there might be one exception to this, depending on how you define your requirements.
> 
> The check_disk command will by default check all the partitions on a given host.  However:
> 
> - the OK/warn/crit will only tell you about 1 partition going warn/crit
> - the length of the string is limited to something like 1K (which is a POSIX limitation, apparently)
> 
> The 1K of informational data is typically reported in a single row; someone recently suggested embedding HTML to format it (which of course would contribute to the usage of the 1K).
> 
> In summary, there are no plugins which do exactly what you're asking, and if you wrote your own, don't be surprised if the voluminous output you're hoping to retrieve gets truncated.
> 
> jc
> 
> 
> > -----Original Message-----
> > From: Jim Mozley [mailto:jim.mozley at exponential-e.com]
> > Sent: Friday, May 02, 2003 9:08 AM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] Single check script to monitor multiple
> > processes
> > 
> > 
> > *This message was transferred with a trial version of 
> > CommuniGate(tm) Pro*
> > Hi all,
> > 
> > I had an idea of something I wanted to do based on experience of using
> > another system management tool. I thought of using one script 
> > to monitor
> > multiple important processes rather than having individual checks.
> > 
> > For instance, if I have a server that runs an mta, dns, 
> > radius and a web
> > server my critical processes might be sendmail, named, 
> > radiusd and httpd.
> > The check could look for the presence of all important 
> > processes and report
> > if one or more were not running, perhaps returning a list of 
> > the failed ones
> > in a message.
> > 
> > Thinking that this might have been done before I started to 
> > look through the
> > plugins but cannot find anything that seems to do this.
> > 
> > Is this because such a thing doesn't exist?
> > 
> > Is this because its an especially bad idea with Nagios?
> > 
> > I can see why one wouldn't want to do this as, for instance, 
> > individual
> > checks allow actions to be taken for different processes. 
> > However, it seems
> > more efficient to check whether a group of processes is not 
> > working rather
> > than putting in place individual checks.
> > 
> > Jim
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS 
> > when reporting any issue. 
> > ::: Messages without supporting info will risk being sent to /dev/null
> > 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null