"service IPs" versus "host IPs"

[Jan Scholten]

> On Mon, Nov 01, 2004 at 06:26:21PM +0000, Ollie Cook wrote:
>> That is to say, host 'foo' may have a management IP 192.168.0.10 (its  
>> "host
>> IP"), but the HTTP service on that host may listen on IP 192.168.1.20  
>> (its
>> "service IP").
> You'll have to define a 'host' for each seperate IP. You don't
> have to monitor the same things on all the hosts though; so you
> could monitor disk space on all of the management IPs and
> specific things on each of the service IPs.

Have you thought of defineing a check_http that accepts a Host Parameter?

in Services:
define service{
		host_name 	 foo
		..
		..
		check_command check_http_host!192.168.1.20
}

checkcommands.cfg:

define command{
		command_name check_http_host
		command_line $USER1$/check_http -H $ARG1$
	}

That works for me!

Jan



-- 
Jan Scholten
Research and Development Intern
Iconz.co.nz


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
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