An email on acknowledge, and onlyonacknowledge? Nagios and RT

[Jason Truong]

Hello folks...

We just implemented RT at our site but its on a different box than the
Nagios server.  Where can I find this patch to Nagios for RT.  The site
I am looking at:

http://archives.free.net.ph/message/20050613.151813.d26c3cb0.en.html

Only works if Nagios and RT are on the same machine.

Any help is appreciated.
Thank you, 


Jason Truong
Plumtree Software
500 Sansome Street Suite 100
San Francisco, CA  94111
email: jason.truong at plumtree.com
phone: (415) 399-7006


-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Chris
Wilson
Sent: Tuesday, July 26, 2005 8:20 AM
To: Nathan Oyler
Cc: Nagios Users
Subject: RE: [Nagios-users] An email on acknowledge, and
onlyonacknowledge? Nagios and RT

Hi Nathan,

> Because if when there's a problem, a notification is sent. A ticket is
> opened.
> 
> Now an hour goes by, and the problem still exists, so another
> notification is sent. Another ticket is opened.
> 
> Now a recovery message is sent. Another ticket is opened.

It's easy enough to write your handler so that no email is sent unless
the message type is ACKNOWLEDGEMENT.

> There's already a patch to Nagios to call the RT api during
> acknowledgements, but my RT machine isn't my Nagios machine, and I
don't
> know enough of anything other than perl to edit it to do as I wish.

perl -i -pe 's/localhost/my.rt.server/g' api-script.c

:-)

> There's also writing handlers to merge tickets when they come in, if
new
> alert comes in, search for if a ticket is created for this host, grab
> that ticket number, send the new alert to comment on the ticket.

This is much trickier. Basically you need to write a mail handler that
gets the responses from RT, captures the ticket number, and associates
it in some way with a permanent record of the problem (maybe hostname +
service name). It's been discussed in the past, you could check the
archives. But it sounds like more than you need.

> This is how I'm leaning if I find nothing else out, but I'm thinking
> just on an acknowledge if a ticket was open, that would make sense.

Cheers, Chris.
-- 
(aidworld) chris wilson | chief engineer (chris at aidworld.org)



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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