To NOT send a message for a particular filter, you need to create a higher-priority filter with an action of 'None'. This will take precedence, but do nothing, so a lower-priority filter can then be set up to send out messages. EG:
Filter 1: Test( messageID==1 ) Action( None )
Filter 2: Test( status==Error ) Action( Critical )
This will send a critical for all 'Error' messages, EXCEPT those with messageID 1.
With the false-matching issue on Win2k8 64bit, I have not been able to duplicate this as I do not have a 64bit development environment. I've not seen it in the 32bit environment, apart from in the past when new eventlogs were added, and the filters became associated with the wrong eventlog. From v1.9.x this should not be possible as the eventlog name/ID are checked on load. The only thing I can suggest is deleting and re-creating the filters, so that they can be certain to have the correct eventlog ID.
You might also be able to run with the 32bit agent but I think it is hard to make it work under 64bit windows.
There is also the ongoing problem with multi-byte characters in the eventlogs foiling any regexp matching and string manipulation in the code.Statistics: Posted by stevesh — Thu Apr 04, 2013 3:25 pm
]]>