per host custom macros

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of David Mansfield
> Sent: Wednesday, March 29, 2006 11:55 AM
> To: Terry
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] per host custom macros
> 
> 
> 
> Terry wrote:
> > You could maybe write an "intelligent" plugin to query the host
> > information from another source based on the service name or
something
> > but nagios needs to know the IP address somehow.  Where would you
want
> > to put this information so nagios can perform the service
> > appropriately?
> >
> 
> 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
> }

To maybe short-circuit this direction --

http://www.nagios.org/development/upcoming.php

User-Defined Object Directives:

Object definitions will be extended to allow for user-defined
variables/directives to be entered. This custom variables will be
inheritable, just like the standard variables now. Custom variables will
likely look something like this...

define host{
	host_name		host1
	...
	_customvar1		"This is a custom variable of some kind"
	_location   		"Host is physically located in Room
301..."
	_snmp_community_string 	public
	}

--
Marc


-------------------------------------------------------
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 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