Nagios showcase project !

[Brad Johnson]

I think the only thing you can do is create a template for each "type" of
host and have each host definition use the template. Will save you some
typing, but you'll still need to create a hostextinfo entry for each
individual host.

Anyone else got an idea for this?

- Brad


On Thu, 25 Sep 2003 andre.bergei at ementor.no wrote:

>  Hi guys, i'm new to the list and nagios.
> 
>   I'm playing around with template config files, and i'm wondering if it is possible to add hostgroups to the hostextinfo.cfg file?
> 
>   Im trying to add the group "Switches" to the "host_name" field, but I cant get i to work. Only real hostnames seems to get the right image file;
> 
> -snip
> 
> define hostextinfo{
>         host_name       Switches, switch01, switches, switch-hosts
>         icon_image      switch40.png
>         icon_image_alt  Network switches
>         vrml_image      switch40.png
>         statusmap_image switch40.gd2
>         2d_coords       100,250
>         3d_coords       100.0,50.0,75.0
> }
> 
> as you see I tried alias, groupname, host-template-name... Only hostname works.
> 
> -snip
> 
> 
> cheers
> /andré
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> 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
> 



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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