[PATCH] - 3.0.3: only send out a service recovery escalation if a service is recovering from a non-OK state listed in the escalation or only 'r' is specified as an escalation option

[Max]

Thomas,

I think I have a resolution to the

tracked escalation state -> non-escalation state 1 ... N -> escalation
recovery -> send recovery

issue you brought up.

In my testing environment I have added code to the patch that will do
the following if the previous problem state is *not* listed explicitly
in the escalation definition:

* If service_history_index > 0
** Walk backwards through the state history for the service no farther
than to the value for  first_notification for the current escalation
*** If any state in the backwards walk matches a state listed in the
escalation definition, then send a recovery notification as that means
we did send an escalation notification for a problem *within the scope
of the current escalation definition*

Do you see any problems with this additional logic?  So far it is
working for me in my test environment, which has the same configs as
our prod environment.

Regards,
Max

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge