service escalation problems
alan.simon at free.fr
alan.simon at free.fr
Tue Jun 7 09:43:03 CEST 2005
Hi all,
I'am using nagios 1.2 on a RedHat EL3.
I'd like to have 3 notifications for an unhandled probleme
1 when the probleme occure
a second 10 minutes later
and the third one hour after the probleme
I've try a lot's off different config and I get itch time
first notification, the second one one minute later and the third 5 minutes
later, even if i change the interval values
thanks for help
here's a config sample :
interval_length=60
define service{
name service_
active_checks_enabled 1
passive_checks_enabled 1
parallelize_check 1
obsess_over_service 0
check_freshness 0
is_volatile 0
notifications_enabled 1
event_handler_enabled 0
flap_detection_enabled 0
process_perf_data 0
retain_status_information 1
retain_nonstatus_information 1
check_period 24x7
max_check_attempts 5
normal_check_interval 2
retry_check_interval 1
notification_interval 10
notification_period 24x7
notification_options w,u,r,c
register 0
}
define service{
use service_
hostgroup_name router
service_description CPU
contact_groups admins
check_command snmp_cpu_cisco!70,68,65!90,88,85
}
define serviceescalation{
hostgroup_name router
service_description CPU
first_notification 2
last_notification 3
notification_interval 50
contact_groups sms
}
define serviceescalation{
hostgroup_name router
service_description CPU
first_notification 3
last_notification 3
notification_interval 0
contact_groups admins
}
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
_______________________________________________
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
More information about the Users
mailing list