A good start would be to implement what I suggest in
https://issues.apache.org/jira/browse/LOG4J2-1010,
add possibility to set the context map in calls to the methods in the
Logger interface.
That would make it possible to implement what I need on top of Log4j 2.
I can't come up with any really c
Mikael,
Any thoughts on how to get this to work for you? Feel free to dig into the
code, we are always looking new for contributors :-)
Gary
On Mon, May 18, 2015 at 10:25 AM, Mikael Ståldal
wrote:
> No, not really.
>
> There is some discussion on this JIRA issue, but it does not solve my
> pro
No, not really.
There is some discussion on this JIRA issue, but it does not solve my
problem:
https://issues.apache.org/jira/browse/LOG4J2-1010
And even my suggestion in the JIRA issue is not ideal solution, just a
possible workaround.
What I really want is something which work like ThreadConte
Mikael,
Did you get any help on this?
Gary
On Fri, May 8, 2015 at 1:51 AM, Mikael Ståldal
wrote:
> I have an asynchronous web app (in Scala based on Twitter Finagle, not
> using Servlet API).
>
> I use Log4j 2.2 for logging, and I want to tag log messages with some
> information about requests
I have an asynchronous web app (in Scala based on Twitter Finagle, not
using Servlet API).
I use Log4j 2.2 for logging, and I want to tag log messages with some
information about requests (such as client IP address and authenticated
user ID).
In a synchronous Servlet based web app, you can use Lo
