On 5/25/2012 7:23 AM, Andreas Ericsson wrote: > They're hardly useful there either, tbh, and if you really need them > you can just put them up as command-line macros before the command you > wish to run, like so: NAGIOS_SOMEVAR="$NAGIOS_SOMEVAR$" > /path/to/something
Sure, that would work, but then you have to enumerate a whole mess of stuff, including new custom fields as added, etc. Would be a lot easier to have a command option to do it. But this is definitely a way to go until that is available (if ever). The way we handle notifications, having access to all those values is very handy since they feed into templates that detail what occurred, what to do, etc. Thanks, Mark -- Mark D. Nagel, CCIE #3177 <mna...@willingminds.com> Principal Consultant, Willing Minds LLC (http://www.willingminds.com) cell: 949-279-5817, desk: 714-495-4001, fax: 714-646-8277 ** For faster support response time, please ** email supp...@willingminds.com or call 714-495-4000 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
