Did this happen, if so how do I drive it.
Just to clarify:
This is what I have
DEBUG|0222-164903753|main|foo.LogStuff|1fac9d11-484a-4fda-8bbf-fa1b9cb5d73c|bCodeGoesHere|cCodeGoesHere|||hello
world
ERROR|0222-164903753|main|foo.LogStuff|1fac9d11-484a-4fda-8bbf-fa1b9cb5d73c|bCodeGoesHere|cCodeGoes
Haven’t even thought about it yet. Probably a couple of weeks. I’d like to
actually see if I can’t work on a couple of Jira issues this weekend.
Ralph
> On Oct 28, 2015, at 11:52 AM, Gary Gregory wrote:
>
> Curious: When are we thinking WRT 2.5?
>
> Gary
>
> On Wed, Oct 28, 2015 at 7:11 AM
Curious: When are we thinking WRT 2.5?
Gary
On Wed, Oct 28, 2015 at 7:11 AM, Ralph Goers
wrote:
> A couple of new features have been added that should help you:
> 1. Log4j now supports a PatternSelector so you can have multiple patterns
> specified for an appender.
> 2. A new unreleased feature
A couple of new features have been added that should help you:
1. Log4j now supports a PatternSelector so you can have multiple patterns
specified for an appender.
2. A new unreleased feature (it will be in 2.5) is the ability to using
Scripting on the PatternSelector. With that you can write a
Hi folks,
I'm looking to migrate from log4j1 to 2 and i'm wondering if there's any
way of making MDC prefixes appear on all stack trace lines. In 1 I had to
override subAppend in RollingFileAppender and I'm hoping I don't need to go
through similar pain in 2.
Thanks
Paul
