Multiple interfaces

[Andreas Ericsson]

jeff vier wrote:
> If you look in the archives, I actually wrote a similar plugin for a
> guy.  I can probably scrounge it up if you need it.
> 
> On Fri, 2004-08-06 at 06:32 -0400, Robert Nelson wrote:
> 
>>> From there, we could move on to adding the capability to 
>>>check_tcp and 
>>>check_http. But the complexity of handling it on a case-by-case basis 
>>>may not be worthwhile for all the plugins. So at some point, 
>>>we may need 
>>>to extend netutils.c to make general way of handling multiple 
>>>interfaces 
>>>-- but I have not thought at all about what such changes 
>>>might look like.
>>
>>Karl, how about a plugin that might be called in the following manner?
>>
>>check_multiple!check_tcp!<normaloptions>
>>
>>Where check_multiple parses the address list and calls check_tcp once
>>for each address?
>>
>>The problem then becomes, do you want the output to say "Reponse of .51
>>seconds; Response of .52 seconds; Response of .48 seconds" or "OK for 3
>>addresses"? What's a warning or crit state? Etc...Given those questions,
>>it might be better off to define it on a per-plugin basis, not sure.
>>

KISS rules apply. One IP-address is one host, as Nagios sees it. That's 
what's intuitive to our customers, and that's the way to keep plugin 
arguments simple enough not to increase the traffic on this rather 
well-manured list already.

>>Rob Nelson
>>Network Engineer
>>Windchannel Communications
>>919-538-6326 
>>

-- 
Andreas Ericsson
OP5 AB


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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