Integration with Request Tracker

Jon Angliss jon at netdork.net
Thu Oct 2 14:24:24 CEST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 02 Oct 2008 11:01:43 +0200, Sebastian Ries
<Sebastian.Ries at dtnet.de> 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
>> 
>> : 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.  
>
>No.
>
>The Order is:
>
>Host goes down
>Notification 1
>Notification 2
>Notification 3
>Host recovers
>Notification 4 (Recovery)
>Host goes down (any)
>Notification 1
>Notification 2
>...

No, that would be $HOSTNOTIFICATIONNUMBER$, not $HOSTNOTIFICATIONID$.

$HOSTNOTIFICATIONNUMBER$
The current notification number for the host. The notification number
increases by one (1) each time a new notification is sent out for the
host (except for acknowledgements). The notification number is reset
to 0 when the host recovers (after the recovery notification has gone
out). Acknowledgements do not cause the notification number to
increase, nor do notifications dealing with flap detection or
scheduled downtime.

$HOSTNOTIFICATIONID$
A unique number identifying a host notification. Notification ID
numbers are unique across both hosts and service notifications, so you
could potentially use this unique number as a primary key in a
notification database. Notification ID numbers should remain unique
across restarts of the Nagios process, so long as you have state
retention enabled. 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.

>Notifications are counted for each problem without regarding other
>problems.

http://nagios.sourceforge.net/docs/3_0/macrolist.html

- -- 
Jon Angliss


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32) - GPGshell v3.64

iEYEARECAAYFAkjkvWwACgkQK4PoFPj9H3OqtQCglQRiHy4JOh+aQ1u0FWi77xa2
7KAAn3QbTsJRuU2gyUmU22rcSDfYPcmW
=Hvq0
-----END PGP SIGNATURE-----


-------------------------------------------------------------------------
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