Question on Using check_disk for multiple partitions

[steve f]

I have a need to check about 10 server partitions on 1200 servers in a distributed Nagios environment.  Down the road, I would probably use event handlers to correct known space issues for certain partitions.

My question is is it significantly more efficient to check all of the partitions in a single check or seperate checks ?  All of the servers being checked are identical in configuration & build and all have the same partitions.

If I run this service check :

check_command                   check_space!15%!10%!/opt!/tmp!/VMware!/test!/var!/work!/steve!/partition1

With this in commands.cfg :

define command {

        command_name    check_space

        command_line    $USER1$/check_by_ssh -H $HOSTNAME$ -C "/usr/local/nagios
/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$ -p $ARG4$ -p $ARG5$ -p $ARG6$
-p $ARG7$ -p $ARG8$" -q

}

This does work,  but I am wondering if I am running the check 1x for each partition listed or is it running 1x and giving me back all partition info. ( kind of like a df -h )

Also, if I run it like this, is there an easy way to configure event handlers to run for the specific partition that has alerted?  Since a space issue in /tmp is not due to the same issue that /work fills up.


Thanks,

Steve
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100908/577f56ab/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
-------------- next part --------------
_______________________________________________
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