You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Pavel_K (JIRA)" <ji...@apache.org> on 2018/10/03 18:45:00 UTC
[jira] [Commented] (LOG4J2-2464) Add possibity for separate logging
for JPMS module/layers
[ https://issues.apache.org/jira/browse/LOG4J2-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637365#comment-16637365 ]
Pavel_K commented on LOG4J2-2464:
---------------------------------
I don't know how log4j is implemented, so I assume the following solution - 1) when logger is created we get the class (for this logger) and get information about module and layer. If we have only String fqdn then we use JDK 9 StackWalker API to get class. 2) information about module and layer we put in MDC. Is this a right approach?
> Add possibity for separate logging for JPMS module/layers
> ---------------------------------------------------------
>
> Key: LOG4J2-2464
> URL: https://issues.apache.org/jira/browse/LOG4J2-2464
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Pavel_K
> Priority: Major
>
> I suggest to add possibility for separate logging for JPMS module/layers. For example, it would be possible to route messages from different modules/layers to separate log files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)