Come on. You got the link to the macro list in the previous thread, couldn't you be bothered to even look at that?
Hint: the macro names end with AUTHOR. Regards Martin Melin On Fri, Feb 12, 2010 at 6:23 PM, Andrew Davis <[email protected]> wrote: > This is a follow-up to my question about including comments in ack emails. I > just tested and ack'd an issue and got an email: > > ***** Nagios ***** > > Notification Type: ACKNOWLEDGEMENT > Host: KVM6 > State: DOWN > Address: 10.5.12.75 > Info: CRITICAL - 10.1.3.75: Host unreachable @ 10.10.45.170. rta nan, lost > 100% > > Date/Time: Fri Feb 12 12:17:58 EST 2010 > > Additional Info: > > Comment: > > Brought down intentionally to test comments in ack emails - From > IP:10.5.7.22 > > How do I see who ack'd this message? Better put, what macro do I use to show > who ack'd an alert? > > -- > > > A. Davis > Email: [email protected] > > "There is no limit to what a man can accomplish > if he doesn't care who gets the credit." - Ronald Reagan > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > 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 > ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ 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
