LOG Event

Wooltown · Post by **Wooltown** » Tue Apr 29, 2003 7:28 am

Hi !

I have a small problem with LOG Event.

Situation: I trigger for an event and when the event has occured, the Bad Status Action is fired, but how do I check for another message in the Event Viewer to fire the Good Status Action ?

Regards
Sven

KS-Soft · Post by **KS-Soft** » Tue Apr 29, 2003 12:24 pm

HostMonitor changes status back to "good" (and starts "good" action) in case there are no NEW "bad" event in the NT Event Log.
If you need to start different actions when different events appear in the log, you can use 2 different "NT Event Log tests" (probably with "Reverse alert" option).

Regards
Alex

Wooltown · Post by **Wooltown** » Tue Apr 29, 2003 1:57 pm

Hello !

That might be a solution, but if I wish to present it on a Custom HTML report and publish it on an intranet web, I have a problem.

For example The first Event could be an error event reporting disk trouble and the second reporting the disk is OK again after the array is fixed, how can I then get it displayed as a "red button" on my report until the secon event ?

Regards
Sven

KS-Soft · Post by **KS-Soft** » Tue Apr 29, 2003 10:13 pm

That's the problem. Sorry, but I don't see good solution in this situation

Just develop another Event Log test...

Regards
Alex

Wooltown · Post by **Wooltown** » Wed Apr 30, 2003 1:12 am

OK, could it be possible for the Event Log tests to have an option, so you manually will have to turn off the alarm (from bad status to OK status) ? Or have another test with a good status running a script that turns off the bad status on the first test ?

Regards
Sven

Marcus · Post by **Marcus** » Thu May 01, 2003 2:08 am

I don't know how eventlog tests work (don't use them), but reading above I see the same problem I had with a cluster environment.

A possible solution could (perhaps) be:
- Create one test, which triggers the 'bad' status.

- As action, execute a scripts, which imports a text file wich changes the test, so it wil now trigger the 'good' status.

- As long as the 'good' status is not found, it should give a red warning.

- When the 'good' status is found, change the test back to its original.

Hope it helps......

KS-Soft · Post by **KS-Soft** » Thu May 01, 2003 11:23 am

Yes, something like that.
Probably better create 2 tests:
Test A) checking for bad event description, does not use "Reverse alert" option, execute Script A when found then event;
Test B) checking for good event description, use "Reverse alert" option, execute Script B when found then event, setup test as disabled;
Script A) disables TestA and enables TestB
Script B) enables TestA and disables TestB

How it will work:
1 - initially) TestA have Good status, TestB is disabled (you can skip disabled tests from the report)
2 - "Bad" event occurs) TestA becames disabled (no report), TestB becomes enabled and changes status to "Bad" (because of "reverse alert" option). It will have "Bad" status until "good" message in the Event Log.
3 - "Good" event occurs) TestB becomes disabled, TestB becomes enabled and changes status to "Good".

A little complicated but I think it will work.

Regards
Alex

Wooltown · Post by **Wooltown** » Mon May 05, 2003 8:41 am

Thanks for the tips, it worked fine except for one thing, in the "test B" I have to test for the Bad Event, not Good Event as you wrote.

I use %Commentline1% in my Custom report so I always display the same name on my report.

Thanks for the excellent service
Sven

KS-Soft · Post by **KS-Soft** » Mon May 05, 2003 12:18 pm

You are welcome. I am glad it works
Alex