<tt>> 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. </tt> <tt>I don't think this is feasible, as it changes Nagios core</tt> <tt>functionality. I don't think I'm the only one wanting</tt> <tt>RECOVERY notifications even from WARNING states. If I define</tt> <tt>it that way, I expect it to behave that way.</tt> <tt>What I do understand is that you want the bug fixed, that</tt> <tt>Nagios sends out RECOVERY to contacts that don't have</tt> <tt>received any CRIT/WARN notification before - I want that</tt> <tt>too ;) I guess you have a similar setup like we do, having</tt> <tt>dozens of escalations with "escalation_options r,c" or</tt> <tt>2 escalations for the same service - one with "c" and one</tt> <tt>with "r", while the "r" escalation is having first_noti 1</tt> <tt>and last_noti 0.</tt> <tt>I've already reported that bug like... 1 year ago - can't</tt> <tt>remember.</tt> <tt>Regards</tt> <tt> Sascha</tt> GFKL Financial Services AG Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Tom Haverkamp Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522