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

Ralph Goers commented on LOG4J2-16:
-----------------------------------

Although Markers are part of 2.0-alpha1 I'm leaving this open in case someone 
wants to implement one of the other techniques mentioned.
                
> Provide support for SLF4J type Markers
> --------------------------------------
>
>                 Key: LOG4J2-16
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-16
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Ralph Goers
>
> We wrote our own logging framework primarily because log4j didn't provide 
> some of the features we needed. One feature was more granularity, especially 
> around logging. We encourage entry and exit tracing, logging of input and 
> output data, logging of elapsed time statistics and several other flavors if 
> "debug" information. Turning all this on in production generates too much 
> data. Our framework supported the concept of Log Type in addition to Log 
> Level. When filtering there was a LogType array where each array element was 
> the log level. The LogRecord contained the LogType and LogLevel so doing 
> filtering was very fast.
> SLF4J supports Markers. These can essentially be used for the same purpose 
> (assuming another Jira issue regarding filtering is implemented). Markers are 
> much more flexible since they can be arbitrarily created. Loggers should then 
> be able to filter on whether a marker is present in addition to the LogLevel. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to