But I want to access the log4j.remoteSourceInfo variable from the log4j
configuration file supplied to the SimpleSocketServer. How can I do that?
Thanks
On Tue, Jul 7, 2015 at 6:34 PM, Ralph Goers
wrote:
> Yes. That property would be in the ThreadContext Map in the log event.
>
> Sent from my i
Yes. That property would be in the ThreadContext Map in the log event.
Sent from my iPad
> On Jul 7, 2015, at 5:32 AM, Sandeep Dasika wrote:
>
> Ralph, thanks for your reply! In the source code for SocketNode, I see this
> line where it sets the following property for the LoggingEvent object:
>
Ralph, thanks for your reply! In the source code for SocketNode, I see this
line where it sets the following property for the LoggingEvent object:
// store the known remote info in an event property
event.setProperty("log4j.remoteSourceInfo", remoteInfo);
and remote info is the remote client addr
I would suggest that you set the ip address in the ThreadContext at the
beginning of each request or operation. Then all log events will contain that
information.
Sent from my iPad
> On Jul 7, 2015, at 12:01 AM, Sandeep Dasika wrote:
>
> Hi log4j team,
>
> I have been using log4j in producti
Hi log4j team,
I have been using log4j in production systems, and it has delivered us
fantastically. My query is around the SocketAppender and SimpleSocketServer
functionality. We have a group of servers that generate log events. These
are configured to write to file appenders. We also want to hav
