escalations question

[Mike Lindsey]

On 10/26/11 10:27 AM, Paul M. Dubuc wrote:
> Michael Barrett wrote:
>> Is there anyway to get that sort of setup working btw?
> You might re-think why you want to do this.  If there has been a problem at
> the warning level for 2 or more notification intervals without it being
> acknowledged (which stops notifications) or fixed, maybe your secondary
> contact should be notified anyway when the critical threshold is exceeded.
When you have multiple levels of management in your escalation trees, 
this particular kind of behavior is to be avoided at all cost.  :)
> If you really want it to work the way you describe then the best solution I
> can think of is to have 2 separate services with different contacts.  One that
> issues only warnings and the other only critical problems.  But then you've
> doubled the number of checks you are doing for the same problem.
>
There's a split-tier notification patch that seems to handle this pretty 
well.  Standard escalation configuration stanzas work the same, but a 
few new ones are added that allow discrete escalations based on 
notification number AND type.  Barring that you'll have to handle it 
some monkey-patched after-thought, in your notification scripts.

You can search the forums (or google) for the patch.  If that fails, I 
can probably find it later.  I believe it was compatible with Nagios 3.2.

-- 
Mike Lindsey


------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning at Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null