I created a custom string match filter to *not* log lines that match a specified string, rather than log filter matches like StringMatchFilter. I also added logic to search the exception if it exists. The logic is all in the Decide method (see code below).
We have a production environment where we're using log4net with Web services. The filter has been working fine for a few weeks until a couple of days ago. Now, for some reason, one of the filters is no longer working. It could be that none of them are working anymore, but we're consistently seeing log messages from one of the filters. Any idea what might cause this? The custom filter Decide method can be viewed here: http://pastebin.com/1PZhyDJd Thanks.
