Why do reverse-alert NTLog monitors fail first time after

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
ixtab
Posts: 32
Joined: Tue Dec 23, 2008 10:37 am

Why do reverse-alert NTLog monitors fail first time after

Post by ixtab »

We have set up a few reverse-alert NTLog monitors to check that specific events appear on a regular basis (once a day/week etc.).
Overall it works beautifully and alerts when some event did not appear in the designated interval, except for this one problem.

Whenever we need to restart the AHM service all these reverse-alert NTLog monitors fail the first time and keep staying on the “Bad” state until their next cycle is due.
It seems like the restart of AHM somehow makes the monitor “forget” where it last looked in the NTLog and starts from the restart time only.
For “weekly” events this can be quite a distraction since it will stay on “Bad” for a week until the next successful eventlog is recorded.

Is there any way around this behavior?

Thanks!
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Yes, this is predefined behaviour - when HostMonitor starts it sets NT Event Log test status to Ok. If you create new NT Event Log test, HostMonitor sets Ok status as well. Then HostMonitor checks for NEW events starting from latest event log record.
If you are using "Reverse alert" option then 1st status will be Bad.

Solution? Sorry do not see any good solution for a moment :( may be because its Sunday :roll:
We will try to find some resolution by Monday...

Regards
Alex
ixtab
Posts: 32
Joined: Tue Dec 23, 2008 10:37 am

Post by ixtab »

Thank you Alex, your help is appreciated.
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Looks like there is no any solution in current version of HostMonitor. So we made some changed in version 7.79: www.ks-soft.net/download/hm779.zip
Please install version 7.78 before using this update.

You may replace hostmon.exe module, add NoReverseAlertFor1stCheck=1 line into [Misc] section of hostmon.ini file and start HostMonitor.
HostMonitor will set Ok status after 1st check (that actually checks connection and collect some information about log but does not check any "old" records) even if "reverse alert" option was enabled, then HostMonitor will work as usually.

Regards
Alex
ixtab
Posts: 32
Joined: Tue Dec 23, 2008 10:37 am

Post by ixtab »

Great! I will give it a try tomorrow and report back.

Thanks!
ixtab
Posts: 32
Joined: Tue Dec 23, 2008 10:37 am

Post by ixtab »

Alex, I can confirm that the solution you provided in v.7.79 works.
I deployed to our test & production systems and all the revrese alerts now don't fire post service restart.

Thank you so much for your ultra-rapid assistance!

Ix.
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

You are welcome :)

Regards
Alex
Post Reply