On 12/16/2010 09:08 PM, stan wrote: > On Thu, Dec 16, 2010 at 05:21:43PM +0100, Andreas Ericsson wrote: >> On 12/16/2010 04:11 PM, stan wrote: >>> We are working on our first Nagios parent chiled system. As I understand >>> it, on the chile I need to invoke something that looks like: >>> >>> /usr/share/nagios/sbin/submit_check_result $HOSTNAME$ '$SERVICEDESC$' >>> $SERVICESTATE$ '$OUTPUT$' >>> >>> That script then does something like this: >>> >>> /usr/bin/printf "%s\t%s\t%s\t%s\n" "$1" "$2" "$return_code" "$4" | >>> /usr/sbin/send_nsca pnoc -c /etc/send_nsca.cfg >>> >>> Ny current issue is that $OUTPUT$ does ot seem to be getting expanded. >>> Insteadit is literaly showing up on the Nagios run time web screen as >>> $OUTPUT$. >>> >> >> Check the docs for what macros are available for obsessive host and >> service check commands. >> >> Or use merlin. It was designed for things like this. >> > losure for the list archives: > > THis sugestion led to a Google search for "Nagios Macors" Which led to a > page listing the macros and "where" they are avail;able. Turns out that the > actual macro is $HOSTOUTPT". > > Question, why does the Nagios parser not complain about invalid macros?
Because they could be environment variables. The syntax for describing macros is a bit fragile. -- Andreas Ericsson [email protected] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Nagios-users mailing list [email protected] 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
