Multiple interfaces

Phil Dibowitz phil at usc.edu
Sat Jul 31 00:49:38 CEST 2004


On Fri, Jul 30, 2004 at 03:32:18PM -0700, PGuth at corp.terralycos.com wrote:
> I guess it depends on what you're trying to do.  If you just want to make 
> sure you're hitting the interface that's closest to the nagios server, 
> then why not simply use *that* interface as the one defined in the host 
> object?  And ignore the rest?
> 
> If you actually need to monitor each interface (or services on each 
> interface) separately I don't see how to avoid the work of defining 
> multiple "things" even if you could find a way to do it without multiple 
> host definitions.  You can make the multiple definitions easier with 
> hostgroups/templating etc so that you only define a service once, assign a 
> hostgroup to it, and put all your hosts (and their interfaces) in that 
> hostgroup.

OK, let me be a bit more clear...

I want all interfaces monitored with each server. However, having to define 10
or 15 services upwards of 5 times for each host gets very unmanagable. It
makes the services.cfg file harder to read, and makes it more likely for
people to make mistakes in it.

Furthermore, it makes the webpage overviews less easy to look at at a glance.
Instead of one:

Host Service
     Service
     Service

to look at, the NOC now has to look at 5 or 8 or 10. The whole point of moving
to nagios is to make things less confusing for the NOC so that us admins get
less 3am calls ;)

Sorry, I should have make that more clear.

Now having said that, if I have to have 5 host definitions and make a host
group out of it, then so be it, I will -- but that just seems unclean to me.
I'll probably make someone here modify the plugins... though we're
understaffed here, so I'd rather not.


-- 
Phil Dibowitz
Systems Architect and Administrator
Enterprise Infrastructure / ISD / USC
UCC 174 - 213-821-5427

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040730/8af8ca75/attachment.sig>


More information about the Users mailing list