Users List
Assunto: RE: chainsaw filtering
Using two sockethubappenders would work well in this case.
Define one socketHubAppender with a debug threshold
Define the other with a warn threshold
Scott
-Original Message-
From: Ricardo Trindade [mailto:[EMAIL PROTECTED]
Sent: Mon 9/20/2004
:
Subject:chainsaw filtering
Hi,
When using chainsaw with a sockethubappender, I imagine that log events
that match the log level of the appender are always passed to chainsaw, and
are the dropped by chainsaw if the GUI is configured to filter them.
I think it would make
Yes, that would be a problem. Perhaps a different appender ?
I think the functionality still makes sense.
-Mensagem original-
De: Stephen Pain [mailto:[EMAIL PROTECTED]
Enviada: segunda-feira, 20 de Setembro de 2004 13:08
Para: Log4J Users List
Assunto: Re: chainsaw filtering
this
cc:
Subject: chainsaw filtering
20/
Hi,
When using chainsaw with a sockethubappender, I imagine that log events
that match the log level of the appender are always passed to chainsaw, and
are the dropped by chainsaw if the GUI is configured to filter them.
I think it would make sense if an option existed (or perhaps
