Multiple hostnames in host_name

[Hari Sekhon]

Fridtjof Busse wrote:
> * Hari Sekhon <hpsekhon at googlemail.com>:  
>   
>> yes, the service definitions can definitely take a list like
>>
>> host_name   host1,host2,host3...
>>     
>
> That's what I'm currently doing.
>
>   
>> Not sure about the macros, check the docs that come with nagios since 
>> they do mention quite a bit about this. It is likely you can define
>> your own $MACROS$ as you want and have all the services update just
>> be restarting the daemon.
>>     
>
> Well, stuff like $USER2$ does not work for me and the docs don't
> mention such a setup (or I didn't find it yet).
>
>   
did you put the $USERn$ definition in a resource file and source it via 
nagios.cfg as follows:

resource_file=/path/to/usermacros.cfg

?

Apparently you are allowed 32 of these.

If you can use hostgroup names instead of host names in services 
definition then this will be better in one way, although it will show up 
in your Status Overview and Status Summary pages which might mess them 
up a bit if you want concise overviews like public webservers, internal 
servers, servers at remote office etc....

-h
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060808/e6f775d3/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- 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