[
https://issues.apache.org/jira/browse/LOG4J2-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-483.
--------------------------------
Resolution: Fixed
I believe the "Logging in the Cloud" section of the manual addresses the title.
> Add a tutorial for distributed logging
> --------------------------------------
>
> Key: LOG4J2-483
> URL: https://issues.apache.org/jira/browse/LOG4J2-483
> Project: Log4j 2
> Issue Type: Documentation
> Components: Documentation
> Reporter: Tal Liron
> Priority: Major
>
> The tutorial should acknowledge two common distributed scenarios with example
> configurations:
> 1) Logging to a database (SQL, NoSQL) via the dedicated appenders
> 2) Logging to a Log4j server via SocketAppender
> The tutorial should specifically address the issue of adding the origin
> information (IP address) to the log message, which is necessary in most
> distributed logging deployments. As Ralph Goers suggest in issue #LOG4J2-476,
> there are two good solutions:
> 1) Use a RewriteAppender with a PropertiesRewritePolicy to inject an
> environment variable (such as HOSTNAME) to the contextMap
> 2) Add properties to specific loggers or the root logger
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
