Am 02.09.2011 19:25, schrieb Wolfgang: > Am 30.08.2011 10:51, schrieb Patricia Jung: >> Hello all, >> >> any hints how to solve the following problem: There's a cronjob running once >> a day. Icinga should monitor whether it had the expected result. Sometimes, >> however, this job is run manually as well, so there's a chance that the >> check result changes during the day, and Icinga should become aware of such >> changes. >> >> Therefore I'd like to define two check_periods: A short one in the morning >> right after the cronjob should have finished, and a long one for the rest of >> the day. >> >> Any idea how to define this? >> >> Thank you >> >> Patricia > I'd consider sending the result as a passive service check. This way you > don't have to mess around with different check periods and the result is > updated as soon as the cronjob ends. Adding freshness checking alerts > you if the cronjob failed to deliver a result. Using "external commands" (http://docs.icinga.org/latest/de/extcommands.html) enables you to alter several options during runtime so "CHANGE_SVC_CHECK_TIMEPERIOD" (http://docs.icinga.org/latest/en/extcommands2.html#extcmd2-change_svc_check_timeperiod) might be the right command this time.
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
