Notifications and state changes WARN and CRIT
Posted: Mon Sep 14, 2015 9:20 am
Hello,
We have XI 2014R2.7.
We have defined a service to check memory.
When this service reaches WARN or CRITICAL it sends notification.
Notification interval is set to 480 mins.
In the example below, a new notification is sent each time a change occurs above the threshold.
Question: Is there a way only to send notification during HARD (from PROBLEM to OK, OK to PROBLEM) changes and not send in the example below, thereby reducing notification emails. I understand that users may want to know during notification interval period when it goes from WARN->CRIT->WARN.
Thanks
[Mon Sep 14 09:46:31 2015] SERVICE NOTIFICATION: it-windows;bed-950-41;Memory Usage;WARNING;xi_service_notification_handler;WARNING - [Triggered by _MemUsed%>85] - Physical Memory: Total: 18GB - Used: 17.044GB (95%) - Free: 978.215MB (5%)
[Mon Sep 14 09:51:31 2015] SERVICE NOTIFICATION: it-windows;bed-950-41;Memory Usage;CRITICAL;xi_service_notification_handler;CRITICAL - [Triggered by _MemUsed%>95] - Physical Memory: Total: 18GB - Used: 17.857GB (99%) - Free: 145.594MB (1%)
[Mon Sep 14 09:56:31 2015] SERVICE NOTIFICATION: it-windows;bed-950-41;Memory Usage;WARNING;xi_service_notification_handler;WARNING - [Triggered by _MemUsed%>85] - Physical Memory: Total: 18GB - Used: 16.107GB (89%) - Free: 1.892GB (11%)
define service {
host_name bed-950-41
service_description Memory Usage
check_period 24x7
check_command check_wmi_mode_only!checkmem -w 85 -c 95!!!!!!!
contact_groups sharepoint_cg,win_cg
notification_period workhours_ev
initial_state o
importance 0
check_interval 5.000000
retry_interval 10.000000
max_check_attempts 36
is_volatile 0
parallelize_check 1
active_checks_enabled 1
passive_checks_enabled 1
obsess 1
event_handler_enabled 1
low_flap_threshold 0.000000
high_flap_threshold 0.000000
flap_detection_enabled 1
flap_detection_options a
freshness_threshold 0
check_freshness 0
notification_options r,w,c,f
notifications_enabled 1
notification_interval 480.000000
first_notification_delay 0.000000
stalking_options n
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
}
We have XI 2014R2.7.
We have defined a service to check memory.
When this service reaches WARN or CRITICAL it sends notification.
Notification interval is set to 480 mins.
In the example below, a new notification is sent each time a change occurs above the threshold.
Question: Is there a way only to send notification during HARD (from PROBLEM to OK, OK to PROBLEM) changes and not send in the example below, thereby reducing notification emails. I understand that users may want to know during notification interval period when it goes from WARN->CRIT->WARN.
Thanks
[Mon Sep 14 09:46:31 2015] SERVICE NOTIFICATION: it-windows;bed-950-41;Memory Usage;WARNING;xi_service_notification_handler;WARNING - [Triggered by _MemUsed%>85] - Physical Memory: Total: 18GB - Used: 17.044GB (95%) - Free: 978.215MB (5%)
[Mon Sep 14 09:51:31 2015] SERVICE NOTIFICATION: it-windows;bed-950-41;Memory Usage;CRITICAL;xi_service_notification_handler;CRITICAL - [Triggered by _MemUsed%>95] - Physical Memory: Total: 18GB - Used: 17.857GB (99%) - Free: 145.594MB (1%)
[Mon Sep 14 09:56:31 2015] SERVICE NOTIFICATION: it-windows;bed-950-41;Memory Usage;WARNING;xi_service_notification_handler;WARNING - [Triggered by _MemUsed%>85] - Physical Memory: Total: 18GB - Used: 16.107GB (89%) - Free: 1.892GB (11%)
define service {
host_name bed-950-41
service_description Memory Usage
check_period 24x7
check_command check_wmi_mode_only!checkmem -w 85 -c 95!!!!!!!
contact_groups sharepoint_cg,win_cg
notification_period workhours_ev
initial_state o
importance 0
check_interval 5.000000
retry_interval 10.000000
max_check_attempts 36
is_volatile 0
parallelize_check 1
active_checks_enabled 1
passive_checks_enabled 1
obsess 1
event_handler_enabled 1
low_flap_threshold 0.000000
high_flap_threshold 0.000000
flap_detection_enabled 1
flap_detection_options a
freshness_threshold 0
check_freshness 0
notification_options r,w,c,f
notifications_enabled 1
notification_interval 480.000000
first_notification_delay 0.000000
stalking_options n
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
}