I'm dealing with a fairly large installation of nagios core 3.3.1 which has gotten a bit long in the tooth. We have some new service checks which we'd like to only notify our DEV teams via email, and not roll through the escalations to the on call admins. My thought was to add these new services to a service group, and then exclude that group from the service escalation configs. However nagios despite parsing the file correctly, it doens't seem to respect the exclusion. The notifications will still escalate even after excluding these, any thoughts? Example config below
Code: Select all
define serviceescalation {
host_name *
hostgroup_name *,!no-escalation
service_description *
servicegroup_name *,!no_escalation
contact_groups sysadmins,oncall,oncall-lvl2
first_notification 2
last_notification 0
notification_interval 10
}
define servicegroup {
servicegroup_name no_escalation
alias No escalation services
notes "These services will not escalate beyond their initial notification"
members cass-node-1,Cassandra Repair,cass-node-2,Cassandra Repair
}
define host {
use standard-linux-host
host_name cass-node-1
alias cass-node-1
address 10.0.0.50
hostgroups +cassandra
}
define service {
use generic-service
hostgroup_name cassandra
service_description Cassandra Repair
active_checks_enabled 0
passive_checks_enabled 1
check_freshness 1
# freshness_threshold set at 26 hours, to allow for some time variation
freshness_threshold 93600
check_command no_sourcecheck_status
normal_check_interval 5
retry_check_interval 1
max_check_attempts 1
contact_groups cassandra-admin
}