[Nagios-devel] 2 new feature requests -- your thoughts

Marc Powell marc at ena.com
Thu Dec 4 14:04:04 UTC 2003


> -----Original Message-----
> From: Ian Holsman [mailto:lists at holsman.net]
> Sent: Thursday, December 04, 2003 3:34 PM
> To: nagios-devel at lists.sourceforge.net
> Subject: [Nagios-devel] 2 new feature requests -- your thoughts
> 
> 
> I was wondering what people thought of the following:
> 
> 
> adding a new command/directive to the service definition to specifiy
the
> arguments passed the reason for this would be to allow the command to
be
> specified in the service template, and you could have the things which
> reference that template just overwrite the arguments passed (ie.. the
> port# or the timeout)

How is this different than what can be done easily with macro
substitution? Using an earlier example,

define command {
	command name check-tcp
	command_line $USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$ -t
$ARG2$
	}

define service {
	host_name foo
	check_command check_tcp!15004!30 #check port 15004 and timeout
after 30 seconds
	}

define service {
	host_name bar
	check_command check_tcp!443!45 #check port 443 and timeout after
45 seconds
	}
> 
> 
> the other idea I had was to add some meta data into some meta-data
into
> the host configuration.
> for example
> 
> META location rack5-position3
> META switchport 4
> META partof SearchingFarm
> 
> which could be referenced by external utilities/guis to enhance the
> alerts/displays.

This functionality already exists (sort of) in the
serviceextinfo:notes_url functionality. What you're calling for is a
tighter integration of that information into nagios itself. I'm not sure
that's the best path. I believe that the type of META information people
would use would be wildly variable ranging from the simple things above
to more complicated items. For example, I've created a script that when
passed a host/service pair will display the relevant customer contact
information, device information, cricket data, most recent Rancid data,
open Remedy ticket information, etc, etc. This is all accessible through
a single click in Nagios.

Now, I'm not discouraging you at all but a more generic notes_url system
(notes.cgi and management of those notes) might be cool to have instead
of just simple META data in the configs.

--
Marc




More information about the Nagios-devel mailing list