On Wed, May 19, 2010 at 3:20 PM, Vladimir N. Indik <[email protected]> wrote: > I want to send notification to three contacts in order. > [email protected] > wait 10 minutes > [email protected] > wait 10 minutes > [email protected] > > My config: > define service { > host_name hostname > service_description servicename > notification_interval 600 #! > max_check_attempts 2 #! > flap_detection_enabled 0 > contacts [email protected] > } > > define serviceescalation{ > host_name hostname > service_description servicename > first_notification 2 > last_notification 2 > notification_interval 600 > contacts [email protected] > } > > define serviceescalation{ > host_name facts > service_description Facts test > first_notification 3 > last_notification 3 > notification_interval 0 > contacts [email protected] > } > > Is it all rihtg? > > I have a problem with this configuration. > When the status changes to OK, the message about it only receives the last > contact (e.g. [email protected]). This is a bug? >
No, it is working as designed. Read up on how escalations work here: http://nagios.sourceforge.net/docs/3_0/escalations.html It is considered best practice to include contacts from lower escalation ranges in higher escalations, because of this exact issue. Quote the above doc: "When defining notification escalations, it is important to keep in mind that any contact groups that were members of "lower" escalations (i.e. those with lower notification number ranges) should also be included in "higher" escalation definitions. This should be done to ensure that anyone who gets notified of a problem continues to get notified as the problem is escalated. " Best regards, Martin Melin ------------------------------------------------------------------------------ _______________________________________________ Nagios-users mailing list [email protected] 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
