> Hi list,
>
> a few days ago I had to mail one of our costumers there warning critical
> values for all his services. That was a really boring job
.>
> For such future tasks it would be very helpful if there could be two
> optional directives "warning" and "critical". Both should be:
> - used be readable by macros ("$WARNING$","$CRITICAL$") to easily
> configure the commands
> - stored inside the object cache
> - columns inside the configuration report through the webinterface.
>
> an example:
>
> define service {
> use generic-service
> host_name foo
> service_description smtp
> check_command check_smtp
> warning 10
> critical 15
> }
>
I foresee a huge amount of moronic questions regarding this from users
who have added the options and removed their command arguments expecting
it to work. Other than that, it's a neat feature.
> define command {
> command_name check_smtp
> command_line $USER1$/check_smtp $HOSTADDRESS$ -w $WARNING$ -c
> $CRITICAL$
> }
>
>
> OK, that won't improve nagios functional
but it won't be so much> work to document then.
>
You could easily hack up some sort of script for this. I'm thinking
grep+sed, or possibly something perl-related.
> Any comments? Any volunteers for coding?
>
> Chers,
>
> Gerd
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Lead Developer
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]