One test using NT Eventlog reports one information-event as "bad" even if the filter says that only "error" and "warning" events should be treated as bad. I've tried to send an e-mail from this event:
Message from HostMonitor (host changed status)
Test : Application Log skskoracle1
Status: Bad
Date : 10/16/2008 9:36:49 AM
Reply : Starter Logonskript
NTEventSource: WSH
NTEventComp: SKSKORACLE1
NTEventType: 0
NTEventID: 0
Here's how the event looks like in the eventviewer:
Event Type: Information
Event Source: WSH
Event Category: None
Event ID: 0
Date: 16.10.2008
Time: 09:36:27
User: N/A
Computer: SKSKORACLE1
Description:
Starter Logonskript
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Here's an export from my test:
;-----------------------------------------------------------------------------
;- HostMonitor`s export/import file -
;- Generated by HostMonitor at 10/16/2008 9:51:18 AM -
;- Source file: C:\Program Files\HostMonitor7\IT-seksjonen.hml -
;- Generation mode: Selected_Tests -
;-----------------------------------------------------------------------------
; ------- Test #01 -------
Method = NTLog
;--- Common properties ---
;DestFolder = Root\skskoracle1\
RMAgent = skskoracle1
Title = Application Log skskoracle1
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 600
Alerts = Send e-mail
ReverseAlert= No
UnknownIsBad= Yes
WarningIsBad= Yes
UseCommonLog= Yes
PrivLogMode = Default
CommLogMode = Default
;--- Test specific properties ---
Computer =
Log = Application
Source =
ReportMode = AllEvents
TestOkMode = ByAcknowledgement
BadFilter = 1
CheckComp = Any
CheckType = AnyFromList
CheckID = Any
CheckDescr = Any
CompList =
TypeList = Error
TypeList = Warning
IDList =
DescrList =
;-----------------------------------------------------------------------------
; Exported 1 items
[/img]
NT Event Log test reports events as "bad" when it
Sorry, cannot explain this problem 
There was issue with old version of HostMonitor, it could detect correct "bad" event but provide information (by macro variables) about near event. This problem was fixed a while ago.
We checked currect code, it should work fine.
Is there some error or warning event in the log around that time (10/16/2008 9:36:49 AM)? Was this event detected as "bad" as well?
Regards
Alex
There was issue with old version of HostMonitor, it could detect correct "bad" event but provide information (by macro variables) about near event. This problem was fixed a while ago.
We checked currect code, it should work fine.
Is there some error or warning event in the log around that time (10/16/2008 9:36:49 AM)? Was this event detected as "bad" as well?
Regards
Alex