Proper use of escalation_options

[Jeff Leyser]

Agreed that's what the documentation says, but that's not what's happening.
 A single WARNING is sent to Group1.  The RECOVERY from that WARNING is
being sent to Group1 and Group2.

-Jeff

On Thu, Apr 12, 2012 at 2:02 AM, Assaf Flatto <nagios at flatto.net> wrote:

> **
> On 11/04/12 23:15, Jeff Leyser wrote:
>
> Greetings!
>
>  Nagios 3.2.3, running on CentOS.  I have two service escalations setup:
>
>  define serviceescalation{
>         servicegroup_name               noncritical
>         first_notification              1
>          last_notification               0
>         notification_interval           10
>         escalation_options              w,r
>         contactgroups                   Group1
> }
>
>  define serviceescalation{
>         servicegroup_name               noncritical
>          first_notification              1
>         last_notification               0
>         notification_interval           10
>         escalation_options              c,u,r
>         contactgroups                   Group2
>  }
>
>  What I want to do is have all WARNINGS and associated RECOVERYs go to
> Group1, while all CRITICAL and UNKNOWNs and associated RECOVERYs go to
> group2.
>
>  For the problem alerts, works great, each group only gets what is
> defined.  But both Group1 and Group2 get all RECOVERY notifications, even
> for problem notifications they don't.
>
>  Is there a way to achieve what I want?
>
>  Many Thanks!
>
>  As is written in the documentation , recoveries will be send to those
> that have all ready been notified about the issue regardless of it's
> current status.
>
> So if the status went from OK  to Warning then to Critical , those in
> Warning  and Critical groups will get the recovery notification.
>
>  http://nagios.sourceforge.net/docs/nagioscore/3/en/escalations.html
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120412/33d07a55/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
-------------- next part --------------
_______________________________________________
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