On 02.08.2013 18:13, Joseph Spenner wrote: > > ------------------------------------------------------------------------ > *From:* Michael Friedrich <michael.friedr...@gmail.com> > *To:* icinga-users@lists.sourceforge.net > *Sent:* Thursday, August 1, 2013 3:29 PM > *Subject:* Re: [icinga-users] changing ping interval > > On 02.08.2013 00:11, Joseph Spenner wrote: > >> I'm trying to change the ping intervals from the default to something > >> much more aggressive: 2s > >> > >> I'm not getting any errors, but it doesn't seem to be working. I'm > >> watching the process list for a ping to the target IP, but it never > >> seems to show up other than my original default of 2 minutes. > >> > >> I tried adding this to my host entry (the man page says to add 's' to > >> indicate seconds. Otherwise, the value is assumed to be minutes) > >> > > which man page are you referring to? never seen such notation in > icinga 1.x > >> > >> > >> check_interval 2s > >> retry_interval 10s > >> > > I saw it here: > > http://nagios.sourceforge.net/docs/3_0/configmain.html#command_check_interval
that's the external command pipe check-for-new-commands poll interval, which is obviously not following the general syntax. > > However, after reading more, I think I may need to adjust this as > well: interval_length ( > http://nagios.sourceforge.net/docs/3_0/configmain.html#interval_length ) speaking of icinga, you should _always_ use the official icinga documentation on http://docs.icinga.org - the nagios documentation is old/outdated/notaccurate anymore, especially when it comes to changes we made in icinga, or added aditional features you may just miss not reading the right documentation for the tool. > > I've noticed my pings are occuring every minute, which would make > sense since the defaul value is 60 seconds. there's an undocumented "feature" - check_interval's can be floats. using that will likely bring your scheduler to death, and it's recommended not to use that default. the reason i was asking - in icinga2, the check_interval syntax is 1s / 1m / 1h [0] so you can identify the current time measurement, and screw such workarounds as interval_length ought to be. we're using icinga2 extensively for tests while implementing the ido component currently. icinga2 being multithreaded, and having timers to run out will allow you to run checks i.e. in 15 secs interval. latency overall depends how fast the check plugins returns, keep that in mind ;-) kind regards, michael [0] http://docs.icinga.org/icinga2/latest/icinga2-tutorial.html (please note that this url is not final. it may change once icinga2 is released as final 2.0) -- DI (FH) Michael Friedrich mail: michael.friedr...@gmail.com twitter: https://twitter.com/dnsmichi jabber: dnsmi...@jabber.ccc.de irc: irc.freenode.net/icinga dnsmichi icinga open source monitoring position: lead core developer url: https://www.icinga.org ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
