A few options: Log4j 1.2.9 or earlier: Write your own Filter class and in decide(loggingEvent), return Filter.DENY if the logger name starts with trace.
Leave the trace events in the log and use Chainsaw and a LogFilePatternReceiver to process the log file (assuming it's a log file). Once the events are in Chainsaw, exclude the 'trace' root node using the logger tree. Log4j 1.3: Use an expressionFilter, with params: expression: ( logger ~= 'trace.' ) acceptonmatch: false -----Original Message----- From: Mustard, Sandy [mailto:[EMAIL PROTECTED] Sent: Fri 3/11/2005 1:57 PM To: Log4J Users List Cc: Subject: How do I exclude some debug tracing? Our developers decided to add some debug level messages for tracing methods calls. They set up a logger that prepends 'trace.' to the class name. Are there any rules that I can set up that I can exclude their 'trace.xxxx' debug statements from showing up when I want debug level logging? Sandy Mustard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
