Issues with notification interval

[lsaspac]

Hey all,

I'm using Nagios XI 2011R2.1

I'm having trouble getting notification-interval to work on a service. I'm trying to get a simple demo working without any templates for troubleshooting. Can anyone tell me where i'm going wrong?

Here is my demo service code. It reliably performs the check and emails me every 1 minute, though seems to ignore the notification_interval where it should limit notifications to every 3 minutes

Code: Select all

define service {
	host_name			my-server-name-here
	service_description		TestEscal Free Space C:
	display_name			Free Space C:
	check_command			check_xi_service_nsclient!Upt1me!USEDDISKSPACE!-l C -w 40 -c 50!!!!!
	is_volatile			0
	max_check_attempts		1
	check_interval			1
	retry_interval			2
	active_checks_enabled		1
	passive_checks_enabled		1
	check_period			24x7
	obsess_over_service		0
	check_freshness			0
	event_handler_enabled		0
	flap_detection_enabled		0
	process_perf_data		0
	retain_status_information	1
	retain_nonstatus_information	1
	notification_interval		3
	notification_period		24x7
	notification_options		w,u,r,c,f,s
	notifications_enabled		1
	contacts			my-contact-here
	register			1
	}

thanks

[mguthrie]

I think your culprits are right here.

Code: Select all

   
max_check_attempts      1
check_interval         1
retry_interval     2

The max_check_attempts is how many check attempts nagios will make before sending an alert about the state change. Right now, Nagios will never retry a check for this service, it will just send an alert. I'm wondering if the 1mn check interval is maybe causing the issue, although you are right in that it *should* still email only every 3 mn. Is this service experiencing frequent state changes, or are you just testing a single state change, and it sends alerts every minute?

[lsaspac]

ok, so there was more to this. I had a service escalation attached which I had forgotten about (apologies). This explains the behaviour in the example

The service escalation had a notification interval of 1 min, which was overriding the notification interval in the service itself

thanks mguthrie

[scottwilkerson]

Glad we have it sorted out.