this format, some or all of this message may not be legible.
------_=_NextPart_001_01C3C0CA.C6BF79F0
Content-Type: text/plain;
charset="ISO-8859-1"
Hm. Interesting that the "obsess_over_service" option in the service
definition documentation has no description
(http://nagios.sourceforge.net/docs/1_0/ ... ml#service).
However, I'm really not 'obsessing' over the service in the nagios sense of
the word. I do not want to run an arbitray command everytime a service check
is run. I'm just looking to send out notifications upon hard state changes -
specifically the change from WARNING to CRITICAL. This was suppressed
artificially when I made notification_interval=0 - which should only apply
to additional notifications when the hard state is the same non-OK state.
Ethan has already commented that this is a bug. I will take a look at the
diffs in the Nagios 1.1 CVS to see what direction he's taking on it
(hopefully the one I want to go in
Tony
--
"Computer science is as much about computers as
astronomy is about telescopes" -- Edsger Dijkstra
---------------------------------------------------------
Anthony Tonns, UNIX Administrator - [email protected]
> -----Original Message-----
> From: Joe Rhett [mailto:[email protected]]
> Sent: Friday, December 12, 2003 4:29 AM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: [Nagios-devel] Forcing hard state change notifications
>
>
> Out of curiosity (not because I know better) what about the
> 'obsessing'
> logic doesn't handle this for you?
>
> On Thu, Dec 04, 2003 at 07:00:14PM -0500,
> [email protected] wrote:
> > I sent in this post almost a month ago. I'm wondering if
> anyone thinks it's
> > a feature worth implementing. I'm not running the latest
> HEAD (I'm at v1.1
> > right now) but I'd be willing to setup a test instance with
> the HEAD, make
> > the alterations, etc. - if it's going to be merged into the
> codebase.
> >
> > It's pretty hard-core when it comes to the nitty gritty of
> the notifications
> > logic. It's taken me some time just to figure out.
> >
> > --
> > "Computer science is as much about computers as
> > astronomy is about telescopes" -- Edsger Dijkstra
> > ---------------------------------------------------------
> > Anthony Tonns, UNIX Administrator - [email protected]
> >
> >
> > > -----Original Message-----
> > > From: [email protected] [mailto:[email protected]]
> > > Sent: Monday, November 10, 2003 6:56 PM
> > > To: [email protected]
> > > Subject: [Nagios-devel] Different paging for different levels
> > >
> > >
> > > Below is a post that I made to the nagios-users list over a
> > > week ago. I
> > > thought about it, and figured that nagios-devel would be the
> > > better place
> > > for it.
> > >
> > > Summary: I'm thinking of some global config variable named
> > > "force_hard_state_change_notification". It would be a
> > > supplement for people
> > > that have "notification_interval=0" to suppress periodic
> > > notifications when
> > > the hard state is the same not-OK state until recovery, but
> > > DO want to know
> > > about other hard state changes while not-OK (ie: a transition
> > > from WARNING
> > > to CRITICAL).
> > >
> > > --- post follows ---
> > >
> > > Whoops. Looks like my assessment was not 100% accurate.
> > >
> > > When a service goes from WARNING to CRITICAL it _is_ a hard
> > > state change.
> > > The problem is that I have notification_interval=0 - which
> > > means since it's
> > > already sent single notification for a non-OK state (the
> > > WARNING) it will
> > > not send another notification for ANY OTHER non-OK state (the
> > > CRITICAL).
> > >
> > > What might be the "feature addition" that would make this
> > > work for me would
> > > be some option to enable some additional logic so that even if the
> > > notification_interval=0, Nagios should ignore the time
> > > interval and attempt
> > > to send a immediate notification (assumin
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]