Running 2.0b6 and I find that these two macros don't evaluate as I
believe they should.
Going on the 2.0 docs, $HOSTALIAS$ seems just as valid as $HOSTNAME$ in
the context of using it for an extended host information macro. In this
case however, $HOSTNAME$ works while $HOSTALIAS$ goes unexpanded.
I'm using the format of having the FQDN be an alias, so as to avoid
having to enter longnames for each entry, service dependency, etc, and
mostly to have the shorter format displayed from the CGI's. I need the
FQDN expressed to pass extended info requests to Ganglia/Cacti pages.
If this is proper behaviour, I can create a hostextinfo stanza for each
DNS group, and make inclusive hostlists, then append the domain to the
end of the url string...
/eli
where:
#extended host info:
define hostextinfo{
hostgroup deathstar-opteron
notes_url
http://overseer/?r=day&c=Opteron+2.4+ghz+Deathstar+Cluster&h=$HOSTNAME$
#vs:
notes_url
http://overseer/?r=day&c=Opteron+2.4+ghz+Deathstar+Cluster&h=$HOSTALIAS$
}
#/extended host info
##### <host>
define host{
use linux-node-production
host_name deathstar2000
alias deathstar2000.domain.name
}
-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users@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
