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-16) Provide support for SLF4J type Markers
Date Sun, 30 May 2010 06:43:36 GMT

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

Ralph Goers commented on LOG4J2-16:

Curt added a "doubt" comment to Logger that said I'd prefer an abstract user context object
over Marker.  You could still use a Marker as your user context object,  but you could also
use an HttpServletRequest or any other context object."

Markers are cheap and fast to filter on but provide a fairly flexible way to segregate logging

When you have an alternative to review please update this issue.

> 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