Integration with Request Tracker

Andreas Ericsson ae at op5.se
Thu Oct 2 16:08:44 CEST 2008


Jon Angliss wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Tue, 30 Sep 2008 15:24:08 +0200, Andreas Ericsson <ae at op5.se>
> wrote:
> 
>> Jim Perrin wrote:
>>> On Tue, Sep 30, 2008 at 3:26 AM, Bo Philip Larsen <boph at tdchosting.dk> wrote:
>>>> This found on nagiosexchange http://www.nagiosexchange.org/cgi-bin/page.cgi?g=Detailed%2F2542.html;d=1
>>> Thanks for this, but the limitation the author lists at the bottom is
>>> just about exactly what I'm running in to. How do you track the ticket
>>> number between nagios and RT?  Tracking the consistent data for the
>>> duration of an issue complicates ticket generation/closure a little
>>> bit :-)
>>>
>>>
>> Nagios 3 introduces notification id's. Once you can connect a
>> notification id and an rt number, you're home free. How to make that
>> connection is up to you though.
> 
> Not directly.  Looking at the description, the ID increases on each
> new  notification sent.  
> 
> : The notification ID number is incremented by one (1) each time a new
> 
> : host notification is sent out, and regardless of how many contacts
> are 
> : notified.
> 
> I read this being that each notification gets a new ID.  For example,
> a host goes down, the first notification gets 1... second gets 2...
> etc.  Host recovers. A service on another host goes down, and the
> notification ID is 3.  
> 
> It'd be a little easier if the notification ID stayed the same for the
> entire duration of the host being down.  
> 
> You might want to look at $SERVICEPROBLEMID$ and $HOSTPROBLEMID$
> instead.  And the $LAST...$ versions of both of those.  Combining with
> an event handler, you can probably use a small table containing the RT
> ticket number, the host/service name, and the problem ID.  You'd then
> feed the state, statetype, service, host, and the problem ID macros to
> the event handler, and you should then be home free :)
> 

Ah, right. Those were the ones I was thinking about. Notification id's
are old news. It's the problem id's that are fresh and good.

Thanks for paying attention :)

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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





More information about the Users mailing list