It seems that log sanitization/addition of properties requires mutability at
some level. Maybe it's a matter of having the mechanism needing to modify
properties tell the framework which attributes it plans on
modifying...but...it is reasonable to expect throwables to be changed after
they are gen
On Sep 23, 2011, at 3:37 AM, Ralph Goers wrote:
>
> On Sep 22, 2011, at 10:16 PM, Curt Arnold wrote:
>
>> Been lurking and watching the thread, wanted to throw some comments out
>> without fully following the thread. Take everything with a grain of salt.
>
> Why? Your input is just as valuable
Extras. I use them to build properties from a Map, add fixed
properties to all events coming off the appender. I could see people
using it to sanitize thread names,parts of thowables or messages as
well.
Scott
On Sep 23, 2011, at 7:33 AM, Ralph Goers
wrote:
Where are those locate
Where are those located?
Ralph
On Sep 23, 2011, at 7:29 AM, Scott Deboy wrote:
> Can you look at rewriteappender and rewritepolicy will fit in? Ability to
> modify the event message and add properties and possibly anything else via
> configuration.
>
>
>
> On Sep 23, 2011, at 12:37 AM, Ral
Can you look at rewriteappender and rewritepolicy will fit in?
Ability to modify the event message and add properties and possibly
anything else via configuration.
On Sep 23, 2011, at 12:37 AM, Ralph Goers
wrote:
On Sep 22, 2011, at 10:16 PM, Curt Arnold wrote:
Been lurking and wat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4j-receivers has an issue affecting its community
integration.
On Sep 22, 2011, at 10:16 PM, Curt Arnold wrote:
> Been lurking and watching the thread, wanted to throw some comments out
> without fully following the thread. Take everything with a grain of salt.
Why? Your input is just as valuable as everyone else's.
>
> log4j 1.2's AsyncAppender does a b
