Am I correct in assuming that if I use irregular schedule in the NT Event Log test and select once a day it will check all events for the 24 hours preceding the time I select?
Or will it just check back to the time the last test executed (Which could be 24 hours or could be less if I do a manual refresh)? Manual has no details on how this works.
Irregular schedule and NT Event Log Test
OK thanks, I missed those few key words as I was searching the manual for "Irregular Schedule" and didn't see a good definition.
In regards to that part of the manual, does that mean if I have to restart the monitoring server that it will no longer check back to the previous test and I will miss all my schedule based NT Event Log tests?
In regards to that part of the manual, does that mean if I have to restart the monitoring server that it will no longer check back to the previous test and I will miss all my schedule based NT Event Log tests?
OK I am wondering how I might mitigate against that risk then. It worries me that if the monitoring server has to be restarted for some reason that we might miss an alert for a customer and get egg on our face (or worse).
I would love to be able to have an NT Event Log Test that you can specify the time range to test and if it misses it then it will re-test.
I would love to be able to have an NT Event Log Test that you can specify the time range to test and if it misses it then it will re-test.
We can add some option to keep track of last event after restart but I am afraid this may lead to other problems 
E.g. you setup NT Event Log test to start alert on every new record. Then you stop HostMonitor for a week or month (or restore backup files). In such case HostMonitor may start thousand alerts...
May be we should add option like "after restart check for all events within last N minutes"
Regards
Alex
E.g. you setup NT Event Log test to start alert on every new record. Then you stop HostMonitor for a week or month (or restore backup files). In such case HostMonitor may start thousand alerts...
May be we should add option like "after restart check for all events within last N minutes"
Regards
Alex
My thoughts, there are many ways to handle this:
Have a user defined setting that tells HM how many hours is too many between the missed scheduled time and the time the test is restarted. For example: 24 hours. If the test was supposed to run more than 24 hours ago then skip it, but maybe have that as the last status (skipped) which could be treated as Unknown or Bad? Otherwise run the test back to the time the last test was run.
Or maybe add a feature whereby you can select the test to either:
1. test back to the last time the test was run (current way it works unless HM was down)
2. test back to last time test was run OR since test/HM was started, whichever is less
3. test back X hours and Y minutes
I probably need to think it through more but I believe that there is a need to have some control over this for reliability and transparency sake. Someone could stop then start HM without letting anyone know and we would not notice that the test did not cover 24 hours of the logs for example.
Have a user defined setting that tells HM how many hours is too many between the missed scheduled time and the time the test is restarted. For example: 24 hours. If the test was supposed to run more than 24 hours ago then skip it, but maybe have that as the last status (skipped) which could be treated as Unknown or Bad? Otherwise run the test back to the time the last test was run.
Or maybe add a feature whereby you can select the test to either:
1. test back to the last time the test was run (current way it works unless HM was down)
2. test back to last time test was run OR since test/HM was started, whichever is less
3. test back X hours and Y minutes
I probably need to think it through more but I believe that there is a need to have some control over this for reliability and transparency sake. Someone could stop then start HM without letting anyone know and we would not notice that the test did not cover 24 hours of the logs for example.