On Tue, Sep 30, 2008 at 9:24 AM, Andreas Ericsson [EMAIL PROTECTED] wrote:
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.
That'll teach me to skim the release notes rather than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 02 Oct 2008 11:01:43 +0200, Sebastian Ries
[EMAIL PROTECTED] wrote:
Hi
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
Angliss
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Integration with Request Tracker
On Thu, Oct 2, 2008 at 4:26 AM, Jon Angliss [EMAIL PROTECTED] wrote:
You might want to look at $SERVICEPROBLEMID$ and $HOSTPROBLEMID$
instead. And the $LAST...$ versions of both of those
-Original Message-
From: Jim Perrin [mailto:[EMAIL PROTECTED]
Sent: Thu 10/2/2008 6:06 PM
To: Jon Angliss
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Integration with Request Tracker
On Thu, Oct 2, 2008 at 4:26 AM, Jon Angliss [EMAIL PROTECTED] wrote:
You might want
Traiano Welcome wrote:
Hi All
How viable would it be to distribute/develop a plugin for NRPE which
is provided with the RT3/NAGIOS distribution and which logs a ticket
directly in the RT database when provided the necessary information
by a nagios server? It seems NRPE plus some plugin code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 30 Sep 2008 15:24:08 +0200, Andreas Ericsson [EMAIL PROTECTED]
wrote:
Jim Perrin wrote:
On Tue, Sep 30, 2008 at 3:26 AM, Bo Philip Larsen [EMAIL PROTECTED] wrote:
This found on nagiosexchange
Hi
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
Jon Angliss wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 30 Sep 2008 15:24:08 +0200, Andreas Ericsson [EMAIL PROTECTED]
wrote:
Jim Perrin wrote:
On Tue, Sep 30, 2008 at 3:26 AM, Bo Philip Larsen [EMAIL PROTECTED] wrote:
This found on nagiosexchange
On Thu, Oct 2, 2008 at 4:26 AM, Jon Angliss [EMAIL PROTECTED] wrote:
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,
This found on nagiosexchange
http://www.nagiosexchange.org/cgi-bin/page.cgi?g=Detailed%2F2542.html;d=1
/Bo
-Original Message-
From: Jim Perrin [mailto:[EMAIL PROTECTED]
Sent: 30. september 2008 04:47
To: Nagios Users mailinglist
Subject: [Nagios-users] Integration with Request Tracker
On Tue, Sep 30, 2008 at 3:26 AM, Bo Philip Larsen [EMAIL PROTECTED] 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
Jim Perrin wrote:
On Tue, Sep 30, 2008 at 3:26 AM, Bo Philip Larsen [EMAIL PROTECTED] 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
Has anyone done integration work or customization of nagios 3.x to at
least pretend to cooperate with request tracker? Some googling has
lead me to
http://lists.bestpractical.com/pipermail/rt-users/2005-June/031775.html
and some modules on the RT wiki for closing tickets, but the methods
seem
13 matches
Mail list logo
