logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Curt Arnold (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LOG4J2-16) Provide support for SLF4J type Markers
Date Mon, 23 Jun 2008 03:48:45 GMT

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

Curt Arnold commented on LOG4J2-16:

I think that this can fit into the "context" concept which is an open ended place for either
explicitly supplied context (like markers would seem to be) or implicit context (such as thread
name, MDC and NDC content, user) that are collected from the environment.    

Not sure how well I described that in the pattern-layout code. 

> 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.
You can reply to this email to add a comment to the issue online.

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

View raw message