Hi,
I've recently upgraded from 1.7 to 1.8, and largely have not had any
issues with the process. There is one oddity that has been plaguing me
since the upgrade, and I can't be sure whether it's actually related or
just arose while I worked on the upgrade.
When services change state back to OK, I get a notification to both the
default contact, and the escalation contact - whether the service
entered into escalation or not. I've included the config for an example
service, which when it changes back to OK from CRITICAL or WARNING after
just one notification, will trigger both a regular OK notification, as
well as a notification to the escalation contact.
This seemed to work correctly prior to the upgrade, however I definitely
wouldn't be surprised to find that it's just coincidence and that I have
an error in my configuration. Appreciate any advice or ideas.
Ross.
===== config sample =====
define service{
use systems-service
host_name ########
service_description Systems Service
check_command check_service
}
define service{
name systems-service
use generic-service
max_check_attempts 3
check_interval 5
retry_interval 2
notification_interval 30
contact_groups systems
register 0
}
define service{
name generic-service
active_checks_enabled 1
passive_checks_enabled 1
parallelize_check 1
obsess_over_service 1
check_freshness 0
notifications_enabled 1
event_handler_enabled 1
flap_detection_enabled 1
failure_prediction_enabled 1
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
is_volatile 0
check_period 24x7
max_check_attempts 3
check_interval 5
check_interval 2
contact_groups systems
notification_options w,u,c,r
notification_interval 5
notification_period 24x7
register 0
}
define contactgroup{
# Systems-related staff and the systems pager
contactgroup_name systems
alias Systems
members systems_pager
contactgroup_members systems_email
}
define contactgroup{
# Just systems-related staff
contactgroup_name systems_email
alias Systems Email Only
members ross
}
define contact{
contact_name systems_pager
use systems_contact
alias Systems Pager
email ############
}
define contact{
contact_name ross
use systems_contact
alias Ross
email ############
}
define contact{
name systems_contact
host_notifications_enabled 1
service_notifications_enabled 1
host_notification_period 24x7
service_notification_period 24x7
host_notification_options d,u,r,f,s
service_notification_options w,u,c,r,f,s
host_notification_commands notify-host-by-email
service_notification_commands notify-service-by-email
can_submit_commands 1
register 0
}
define serviceescalation{
use systems-service-escalation
host_name #########
service_description Systems Service
}
define serviceescalation{
name systems-service-escalation
first_notification 7
last_notification 0
contact_groups systems,systems-escalate
register 0
}
define contactgroup{
contactgroup_name systems-escalate
alias Systems Escalation
members esc_systems_pager
contactgroup_members systems_email
}
define contact{
contact_name esc_systems_pager
use systems_contact
alias Systems Escalation Pager
email ###########
host_notification_commands escalate-host-by-email
service_notification_commands escalate-service-by-email
}
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
