Hello,
Is it possible to get "Time Restriction" working in only "Time Restriction" mode?
I am sure that not only me but lots of other ppl will find this feature very usefull if it will get back to "Alerting Time" in the same way just like the regular monitoring does.
So, if at the time of the first run after the "Quiet Time" had passed, Host Monitor will detect that tested system is already in a fault and a number of faulty tests, even during a "Quiet Time" is not less than the number of faulty tests requested in "Start When..."- it will send an appropriate alert?
Thanks,
Gluk.
"Time Restriction" option
Please first implement this
Then we have to take a closer look.
But please create some more variables and count
- only the tests in the specified folder
- all tests in folder and all subfolders
Then we can run a single test at start of day (i.e. 6 a.m.) that can send an eMail with "All test are OK" or "There are %::FolderName::BadTests% tests with a problem".KS-Soft wrote:We plan to implement variables like %::FolderName::GoodTests%, %::FolderName::BadTests%. Then "test depends on expression %::FolderName::BadTests%>0" option will do the trick.
Regards
Alex
Then we have to take a closer look.
But please create some more variables and count
- only the tests in the specified folder
- all tests in folder and all subfolders
Implemented since 7.00 Beta
New feature: Deferred actions. "Time restriction" option allows you to suppress action execution depending on time of the day and/or day of the week. Additional "Deferred action" option tells HostMonitor to delay action execution if specified schedule does not allow immediate execution of the action. HostMonitor will execute action at the beginning of "allowed" time frame on condition that status of the test is identical to status that triggered alert.
Note1: If the same test triggers the same action several times within "restricted" time frame, HostMonitor will execute action just once at the beginning of "allowed" time frame.
Note2: When HostMonitor starts deferred (delayed) action, macro variables will be resolved with using of current (up to date) test status, current date and time, current status of HostMonitor, etc.
Note3: HostMonitor considers the following statuses as identical
- Bad = Bad contents = No answer
- Ok = Host is alive = Normal
- Unknown = Unknown host
Also "Warning" status can be considered as identical to "Bad" when "Treat Warning status as Bad" option of the test item is enabled. The same is true for "Unknown" and "Unknown host" statuses when "Treat Unknown status as Bad" option is enabled.
Great ! Many thanks
Juergen
New feature: Deferred actions. "Time restriction" option allows you to suppress action execution depending on time of the day and/or day of the week. Additional "Deferred action" option tells HostMonitor to delay action execution if specified schedule does not allow immediate execution of the action. HostMonitor will execute action at the beginning of "allowed" time frame on condition that status of the test is identical to status that triggered alert.
Note1: If the same test triggers the same action several times within "restricted" time frame, HostMonitor will execute action just once at the beginning of "allowed" time frame.
Note2: When HostMonitor starts deferred (delayed) action, macro variables will be resolved with using of current (up to date) test status, current date and time, current status of HostMonitor, etc.
Note3: HostMonitor considers the following statuses as identical
- Bad = Bad contents = No answer
- Ok = Host is alive = Normal
- Unknown = Unknown host
Also "Warning" status can be considered as identical to "Bad" when "Treat Warning status as Bad" option of the test item is enabled. The same is true for "Unknown" and "Unknown host" statuses when "Treat Unknown status as Bad" option is enabled.
Great ! Many thanks
Juergen