Nagios xi passive reporting to server staggering approach

benjaminsmith · Post by **benjaminsmith** » Wed Nov 04, 2020 12:04 pm

Hi @mrjsokol,

I received your PM message, can you re-attach the newest profile? It wasn't included for some reason and I was unable to find those hosts in the last profile. However, I did track down WENDYS-ORDER-02.

Try increasing the freshness threshold as this value is in seconds on this host to avoid any false positives ( when check_dummy is executed and the host is set to non-ok state) and let me know if that resolves that issue.

Code: Select all

define host {
	host_name	US - WENDYS-ORDER-02
	alias	US - WENDYS-ORDER-02
	check_period	xi_timeperiod_24x7
	check_command	check_dummy!2!“Host $HOSTNAME$ has not checked in” !!!!!!
	contacts	Contact Name
	contact_groups	Contact Group
	notification_period	xi_timeperiod_24x7
	initial_state	o
	importance	0
	check_interval	5.000000
	retry_interval	1.000000
	max_check_attempts	5
	active_checks_enabled	0
	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	65
	check_freshness	1
	notification_options	d,u
	notifications_enabled	1
	notification_interval	60.000000
	first_notification_delay	0.000000
	stalking_options	n
	process_perf_data	1
	icon_image	passiveobject.png
	statusmap_image	passiveobject.png
	retain_status_information	1
	retain_nonstatus_information	1
	_xiWIZARD	passiveobject
	}

References
https://assets.nagios.com/downloads/nag ... hness.html
https://assets.nagios.com/downloads/nag ... .html#host

mrjsokol · Post by **mrjsokol** » Thu Nov 05, 2020 11:37 am

Hello Benjamin,

Any new news on the result of review of the profile?

ssax · Post by **ssax** » Thu Nov 05, 2020 4:10 pm

I think Benjamin is right about this, do the other hosts/services have a freshness threshold of 65?

Are your passives being sent in every minute or every five minutes (the default)?

If your freshness is set to 65 seconds but the remote agent only sends it in every 300 seconds (5 minutes, the default) you can safely assume you will see that "CRITICAL - Host $HOSTNAME$ has not checked in" a lot. If they are indeed sending every 5 minutes you should go a little higher than what that interval is for the freshness_threshold (like changing the freshness_threshold to 330 or something, even going 10 minutes would be fine). That freshness setting is saying, if I haven't seen a result in X amount of time, run the check_command (which is currently set to show "CRITICAL - Host X has not checked in") so that's likely what you are seeing.

Does that make sense?

mrjsokol · Post by **mrjsokol** » Thu Nov 12, 2020 9:38 am

Thanks guys, I think after a few days of testing we were able to mitigate a lot of false positives from changing the rate from 65 to 125 for freshness check. I think we can lock this thread at this point.

benjaminsmith · Post by **benjaminsmith** » Fri Nov 13, 2020 10:26 am

Hi,

Thanks guys, I think after a few days of testing we were able to mitigate a lot of false positives from changing the rate from 65 to 125 for freshness check. I think we can lock this thread at this point.

Great! We'll close this out.

Thank you for using Nagios.

Nagios Support Forum

Nagios xi passive reporting to server staggering approach

Re: Nagios xi passive reporting to server staggering approac

Re: Nagios xi passive reporting to server staggering approac

Re: Nagios xi passive reporting to server staggering approac

Re: Nagios xi passive reporting to server staggering approac

Re: Nagios xi passive reporting to server staggering approac