Hi there, The problem in short: the escalations are working like a charm, but the notification interval of the escalation seems to be ignored. In more detail, the configuration is as follows:
| define serviceescalation {
| first_notification 1
| last_notification 0
| notification_interval 900
| contact_groups cg-all-sane
| service_description $service
| host_name $host
| escalation_options r,w,u,c
| }
| define serviceescalation {
| first_notification 12
| last_notification 0
| notification_interval 3600
| escalation_period twentyfourseven
| contact_groups cg-storingsdienst-escalatie
| service_description $service
| host_name $host
| escalation_options r,c
| }
| define serviceescalation {
| first_notification 4
| last_notification 0
| notification_interval 1800
| escalation_period twentyfourseven
| contact_groups cg-storingsdienst
| service_description $service
| host_name $host
| escalation_options r,w,u,c
| }
| interval_length=1
| define service {
| name s
| register 0
| max_check_attempts 6
| normal_check_interval 120
| retry_check_interval 20
| check_period twentyfourseven
| notification_interval 300
| notification_period twentyfourseven
| notifications_enabled 1
| register 0
| notification_options w,u,c,r,f
| contact_groups cg-all-insane
I believe this would, in case of a long lasting problem, result in:
- a notification to all contacts in cg-all-sane every 15 minutes, starting
immediatelly when there is a problem
- a notification to all contacts in cg-storingsdienst every 30 minutes if
problem has not been resovled or acknowledged within 20 minutes
- a notification to all contacts in cg-storingsdienst-escalatie every 60
minutes if problem has not been resovled or acknowledged within 1 hour
There are no overlaps in contacts between the various contactgroups (I have
created separate e-mailaddresses to be notified, to avoid problems).
Testing this setup resulted in the following notifications:
07:50:44 cg-all-sane
08:07:32 cg-all-sane
08:24:32 cg-all-sane
08:41:24 cg-all-sane, cg-storingsdienst
08:58:19 cg-all-sane, cg-storingsdienst
09:15:10 cg-all-sane, cg-storingsdienst
09:32:16 cg-all-sane, cg-storingsdienst
09:49:25 cg-all-sane, cg-storingsdienst
10:06:31 cg-all-sane, cg-storingsdienst
10:23:38 cg-all-sane, cg-storingsdienst
10:40:38 cg-all-sane, cg-storingsdienst
10:57:40 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
11:14:46 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
11:29:49 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
11:46:58 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
After this the problem was resolved. I am happy with the escalation, but the
thing that does not work is the notification interval. It seems the setting
is being ignored. What is it I am doing wrong here?
Thank you in advance for your help. It's the only showstopper for the
implementation of this nagios instance... :)
PS. Only modifications to config bits above are a replacement of service and
host.
--
Rejo Zenger <[EMAIL PROTECTED]> https://rejo.zenger.nl
signature.asc
Description: Digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Nagios-users mailing list Nagios-users@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
