Re: [Wrapper-user] Logging filter enhancement

[Leif M. <le...@ta...>]

Mark,
In your last message, you said that you were going to use the Wrapper log
methods to control log output.  One option would be to send the output at
the DEBUG level.  this way it would not be displayed in the console, or the
wrapper.log file by default.

Otherwise,  I would suggest using Log4j or Avalon's LogKit to handle
logging from within the JVM.  They will do a much better job than the
Wrapper is capable of doing from outside.

Features have slowly been added to the Wrapper's logging over time in
response to user needs, but it is not designed to be a replacement for
a real logging system inside the JVM.   Most applications that I write 
handle
all logging within the JVM by sending application output to a dedicated log
file.  Only error messages are displayed to the console.  This keeps the
contents of the wrapper.log file fairly simple and dedicated to startup,
shutdown, and critical errors.  I know it is all personal preference though.

I'll give your request some thought.  Each filter adds some load to the
system as all log output must be scanned against each registered filter.
What you are asking for is to be able to hide an entire line of output if
that output contains a specified token?

Cheers,
Leif

Mark Phippard wrote:

>Would it be possible to add an action of IGNORE to wrapper.filter.action? 
>IGNORE would mean to not write the message to the log.
>
>I would like to use this to enter some log messages as triggers that we 
>would rather not write to the log.  I have a process where I am logging 
>all of the messages retrieved after running a system command.  Some of 
>these messages are just copyrights etc..  It would be nice if I could 
>filter them out in the logging framework instead of in my code.  That way 
>the user could control it, and if the copyrights changed I could just 
>filter them out by updating the wrapper.conf.
>  
>