logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-476) Add source host to log event for distributed logging
Date Thu, 02 Jan 2014 05:22:50 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860021#comment-13860021

Ralph Goers commented on LOG4J2-476:

I am unsure what is being asked here.  Why is setting a ThreadContext key named "hostname"
to the correct hostname insufficient? http://logging.apache.org/log4j/2.x/manual/eventlogging.html
shows something similar to what was done with my former employer.

> Add source host to log event for distributed logging
> ----------------------------------------------------
>                 Key: LOG4J2-476
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-476
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0-beta9
>            Reporter: Tal Liron
>            Priority: Critical
> It's absolutely necessary to support this: when logging centrally, you *need* to know
from where the log message arrived. I've marked the issue as critical, because log4j is not
very useful without it in distributed environments. If you don't know where the log message
came from, it's close to worthless.
> This applies at least to all classes that inherit from AbstractDatabaseAppender, but
I think the solution should be more generic: developers might create their own appenders that
would require this information. It can be handled, I think, in the same way as LogEvent.setIncludeLocation:
allow all loggers to include this information if configured to do so.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message