I don't know if you have a real use of the "host_alias", but if not, you could
maybe use this field to stock your customized definitions. You should also
change the notification scripts to send the $HOSTNAME$ and not the
$HOSTALIAS$ value....
you would have something like :
host_alias $CUSTVAL1;$CUSTVAL2;$CUSTVAL3;...
Ok, it is a bit tricky, but well, it think it could work...
Johan
Le Mercredi 29 Mars 2006 21:06, David Mansfield a écrit :
> jeff vier wrote:
> > On Wed, 2006-03-29 at 12:55 -0500, David Mansfield wrote:
> >> Something like:
> >>
> >> define host {
> >> use generic-host
> >> host_name myhost.mydomain.com
> >> alias myhost
> >> address 1.2.3.4
> >>
> >> custom_macro FOOPROPERTY=AA:BB:CC:DD
> >> custom_macro BARVALUE=BigImportantValue
> >>
> >> hostgroups all_foo,all_bar
> >> }
> >>
> >> With:
> >>
> >> define hostgroup {
> >> name all_foo
> >> alias all_foo
> >> }
> >>
> >> define service {
> >> hostgroup_name all_foo
> >> check_command check_foo
> >> }
> >>
> >> And finally, the payoff:
> >>
> >> define command {
> >> command_name check_foo
> >> command_line $USER1$/check_foo -f $FOOPROPERTY$
> >> }
> >
> > You've pretty much exactly described $ARG1$, $ARG2$, ... $ARGn$
>
> No. I'm sorry but you are missing the point. $ARG1$ blah blah are
> specified in the 'service' object.
>
> That means you HAVE to define a service object for every host/service
> combination. Yuk! Right now you can apply a service to an entire
> _hostgroup_, and the assignment/memebership to the hostgroup is set up
> IN the host object. This means that for those services, all the
> information necessary is captured in the host definition, as long as
> only the standard attributes (hostaddress etc) are referenced.
>
> Why should I configure the XYZ property of my host anywhere other than
> the host definition? It doesnt' make one lick of sense from a
> management perspective.
>
> Not to mention it forces twice the management burden to have to copy
> service definitions all over the place.
>
> David
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live
> webcast and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> 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
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
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
