logging-log4j-dev mailing list archives

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

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

Tal Liron commented on LOG4J2-476:

What you say is possible only when users explicitly use EventLogger and explicitly set the
hostnaame. But this feature must be available for *all* logged messages, even when using the
alternate APIs (log4j 1.2, SLF4J), and it should be automatic. Even if I'm running an old
legacy library, I still need to know from which node it originated. That's why I'm saying
that it should be handled at the appenders  -- it is not the duty of the caller to explicitly
set it.

> 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