Hello,
I have an unusual request - I think, not sure if Nagios can do this.
I've been asked on a service I put in
1. Can we have it run every 30 minutes? If I rerun data I wouldn’t want it to send an email every 3 minutes.
2. Also it will not run from 11CST to 5CST while cycles and hours are processing correct?
so I believe I resolved the run every 30 minutes... by setting the check_interval to 30 minutes and retry of 5 minutes
#use symbolic link on Windows 2012 server
# D:\>mklink /D ApmLoader "D:Delta Incoming\IncomingData\PersistentStore\Delta IBM MQ Series"
define service {
host_name GEIPALPDLTPRC01
service_description Delta File Count
check_command check_ncpa!-t 'gold3726' -P 5693 -M 'plugins/check_files.vbs' -a '-p 'D:\\ApmLoader' -w 200 -c 200'
max_check_attempts 5
check_interval 30
retry_interval 5
check_period 24x7
notification_interval 60
notification_period 24x7
contact_groups Delta-Admins
register 1
}
not sure how or if can be done NOT to RUN checks between 11CST to 5CST.
is there a way with the below parameter?
check_period 24x7
how to specify an off time in the check interval or...
Re: how to specify an off time in the check interval or...
This is the handiest link you can have when working with Nagios Core.
https://assets.nagios.com/downloads/nag ... tions.html
check_interval is the time between service checks, usually in minutes, but I believe that's configurable as well.
retry_interval kicks in when a service check returns a non-OK result. Nagios will re-check the service up to the max_check_attempts using retry_interval as the time between checks until max_check_attempts has been reached. Once max_check_attempts has been reached, assuming it's still a non-OK status, the service enters into a hard non-OK state, event handlers kick off, and notifications go out.
check_period can be configured in the file /usr/local/nagios/etc/objects/timeperiods.cfg.
https://assets.nagios.com/downloads/nag ... tions.html
check_interval is the time between service checks, usually in minutes, but I believe that's configurable as well.
retry_interval kicks in when a service check returns a non-OK result. Nagios will re-check the service up to the max_check_attempts using retry_interval as the time between checks until max_check_attempts has been reached. Once max_check_attempts has been reached, assuming it's still a non-OK status, the service enters into a hard non-OK state, event handlers kick off, and notifications go out.
check_period can be configured in the file /usr/local/nagios/etc/objects/timeperiods.cfg.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: how to specify an off time in the check interval or...
thank you! I will try this and post results.
and thanks for the link
wow! ok, I see what you are saying... thank you. gee, after all this, I'm gonna be a Nadios Core PRO
thanks to you!
this ticket can be closed.
and thanks for the link
wow! ok, I see what you are saying... thank you. gee, after all this, I'm gonna be a Nadios Core PRO
this ticket can be closed.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: how to specify an off time in the check interval or...
Great!gmills wrote:thank you! I will try this and post results.
and thanks for the link
wow! ok, I see what you are saying... thank you. gee, after all this, I'm gonna be a Nadios Core PROthanks to you!
this ticket can be closed.
Locking