Nagios Support Forum

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 00297AFFC12575F9_=
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: quoted-printable

> In this case we would receive recovery service escalations for
> services returning to OK from WARNING when we never were sent a
> WARNING escalation notification because it is not a state listed in
> escalation_options. With the patch a recovery is only sent if the
> previous state of the service was CRITICAL and an escalation
> notification had been sent out because the escalation rule had
> previously matched on CRITICAL.

I don't think this is feasible, as it changes Nagios core
functionality. I don't think I'm the only one wanting
RECOVERY notifications even from WARNING states. If I define
it that way, I expect it to behave that way.

What I do understand is that you want the bug fixed, that
Nagios sends out RECOVERY to contacts that don't have
received any CRIT/WARN notification before - I want that
too I guess you have a similar setup like we do, having
dozens of escalations with "escalation_options r,c" or
2 escalations for the same service - one with "c" and one
with "r", while the "r" escalation is having first_noti 1
and last_noti 0.

I've already reported that bug like... 1 year ago - can't
remember.

Regards
Sascha



GFKL Financial Services AG
Vorstand: Dr. Peter J=C3=A4nsch (Vors.), J=C3=BCrgen Baltes, Dr. Tom Haverk=
amp
Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma
Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522
--=_alternative 00297AFFC12575F9_=
Content-Type: text/html; charset="utf-8"
content-transfer-encoding: quoted-printable

> In this case we would receive recovery service esca=
lations
for
> services returning to OK from WARNING when we never were sent a
> WARNING escalation notification because it is not a state listed in
> escalation_options.  With the patch a recovery is only sent if
the
> previous state of the service was CRITICAL and an escalation
> notification had been sent out because the escalation rule had
> previously matched on CRITICAL.

I don't think this is feasible, as it changes Nagios
core
functionality. I don't think I'm the only one wantin=
g
RECOVERY notifications even from WARNING states. If
I define
it that way, I expect it to behave that way.

What I do understand is that you want the bug fixed,
that
Nagios sends out RECOVERY to contacts that don't hav=
e
received any CRIT/WARN notification before - I want
that
too I guess you have a similar setup like we do,
having
dozens of escalations with "escalation_options
r,c" or
2 escalations for the same service - one with "=
c"
and one
with "r", while the "r" escalati=
on
is having first_noti 1
and last_noti 0.

I've already reported that bug like... 1 year ago
- can't
remember.

Regards
        Sascha



GFKL Financial Services AG
Vorstand: Dr. Peter J=C3=A4nsch (Vors.), J=C3=BCrgen Baltes, Dr. Tom H=
averkamp
Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma
<span style=3D"font-family:sans-serif,helvetica; font-size:10pt; color:#000=

...[email truncated]...


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