I'm writing a custom filter (inherits from FilterSkeleton) and I want to log
errors inside the filter.  The problem is that any log events created inside
the filter is not getting logged.  Is there a special restriction that log
events cannot be created this far down inside the loggin pipeline?

public override FilterDecision Decide(LoggingEvent loggingEvent)
{
    // Do the interesting stuff

    // In some exceptional case, log an error
    LogManager.GetLogger("TheLogger").Error("log message", exception);
}

Any reason why this code wouldn't work?
--
View this message in context: http://www.nabble.com/Log-not-logging-in-custom-filter-tp23624032p23624032.html
Sent from the Log4net - Users mailing list archive at Nabble.com.

stefan.moser wrote:
> I'm writing a custom filter (inherits from FilterSkeleton) and I want to log
> errors inside the filter.  The problem is that any log events created inside
> the filter is not getting logged.  Is there a special restriction that log
> events cannot be created this far down inside the loggin pipeline?
>
> public override FilterDecision Decide(LoggingEvent loggingEvent)
> {
>     // Do the interesting stuff
>
>     // In some exceptional case, log an error
>     LogManager.GetLogger("TheLogger").Error("log message", exception);
> }
>
> Any reason why this code wouldn't work?
>  

Inside of the log4net framework, there is an internal logger called
LogLog.  It's used throughout the appender framework, but I imagine
there's no problem using it in a filter.

Just call:

LogLog.Error("log message");


~Loren

Thanks Loren, that's exactly what I'm looking for.

Cheers,
Stefan