Why the distinction between host definition and hostextinfo definition?

[Marc Haber]

Hi,

to me, the distinction between host definition and hostextinfo
definition seems artificial, awkward and clumsy - and it prevents some
of the more powerful features from being used with the information
that belongs into hostextinfo. 

Hostextinfo doesn't seem to support templates, and it doesn't seem to
be possible to set information that is set as hostextinfo from a host
group or via wildcards.

This makes it extraordinarily hard to - for example - set host icons
for the status map, since it needs a dedicated hostextinfo
definition setting icon_image and statusmap_image for each host which
might have all other properties set from a template.

Is there any reason for keeping this distinction and not including
hostextinfo into main configuration?

Am I missing something here?

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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