Single check script to monitor multipleprocesses

[Subhendu Ghosh]

On Wed, 7 May 2003, Jim Mozley wrote:

> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> Sorry for the late response to my original post, been aware from work and
> have had a public holiday here in the UK. Thanks for all the responses.
> 
> > Off-hand, I see no other particularly strong reasons for grouping the
> > functionality at the development level. Do you?
> >
> > And if you do, could that need be resolved with a generic aggrgator that
> > allows poeple to lump unit plugins to their taste instead of creating
> > one bloated plugin that has 20 capabilities of which only 2 might be
> > used on a given call?
> >
> 
> I agree that this might become a problem if any monitor script tries to do
> too much. The biggest problem I see with one script that checks for a list
> of processes running is that this makes it difficult to tailor individual
> corrective action appropriate to the application. However, I have in the
> past used one script that has checked to see if a list of processes is
> running in conjunction with individual monitors that check things like DNS
> queries being answered or DHCP issuing leases, etc.
> 
> The dual approach is aimed at working out whether the service is running
> from a customer point of view and also trying to identify the cause of the
> problem (such as the process isn't working).
> 

Then what you want is service dependencies, where te customer facing check 
is dependent on all the back end checks.

-- 

-sg



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
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