Re: [Nagios-devel] Notifications on 2nd critical transition

[Guest]

--Apple-Mail-195-212386613
Content-Type: text/plain;
charset=US-ASCII;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit


On 22 Oct 2010, at 05:45, Ton Voon wrote:

> Hi!
>
> Just a little heads up that there is a change committed into Nagios
> which one of our customers for Opsview had noticed. If you
> transition a service from:
>
> 1) ok
> 2) warn
> 3) critical
> 4) warning
> 5) critical
>
> There is a notification at (2) and (3) but not at (5), which is
> counter-intuitive. The change now causes (5) to notify.

An IRC conversation with Holger has made me re-evaluate this change. I
think the requirements are satisfied by use of the "sticky" option for
acknowledgements.

I've written up my findings re: acknowledgments here: http://wiki.nagios.org/index.php/Acknowledgementlogic

So I think that the code change is no longer required and I've just
backed it out.

Ton


--Apple-Mail-195-212386613
Content-Type: text/html;
charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On 22 Oct 2010, =
at 05:45, Ton Voon wrote:Hi!Just a little heads up that there is a =
change committed into Nagios which one of our customers for Opsview had =
noticed. If you transition a service from:  1) ok =
 2) warn  3) critical  4) warning  5) =
criticalThere is a notification at (2) and (3) but not at (5), =
which is counter-intuitive. The change now causes (5) to =
notify.An IRC conversation with =
Holger has made me re-evaluate this change. I think the requirements are =
satisfied by use of the "sticky" option for =
acknowledgements.I've written up my findings re: acknowledgments =
here: http://wiki=
.nagios.org/index.php/AcknowledgementlogicSo I think that =
the code change is no longer required and I've just backed it =
out.Ton=

--Apple-Mail-195-212386613--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]