Your configuration is not a great way to do it. Every event that passes the
log level will get passed to the appender for filtering by user. This is more
expensive than having the filter be a turbo filter.
The way I would handle this is to use the DynamicThresholdFilter. If you want
each user to log to a separate file then use the SiftingAppender to route the
log events to a log file for that user regardless of the logger.
The configuration below accepts the event if it is from a specific user
regardless of its level. All others flow through unimpeded. Unfortunately, if
you don't want debug events for the user logged to LEGACY or STDOUT then you
will need to add a ThresholdFilter to those two appenders. However, this isn't
as bad since they will only be for that single user.
Notice I specified the log level on all the loggers. IMO this is better in
practice because a) the hierarchy doesn't have to be searched all the way to
the parent on each event so it will perform better and b) it is less confusing
to people looking a the configuration, especially when you specify additivity.
<configuration>
<turboFilter class="ch.qos.logback.classic.turbo.DynamicThresholdFilter">
<Key>userId</Key>
<DefaultThreshold>WARN</DefaultThreshold>
<onLower>NEUTRAL</onLower>
<onHigherOrEqual>ACCEPT</onHigherOrEqual>
<MDCValueLevelPair>
<value>123456</value>
<level>DEBUG</level>
</MDCValueLevelPair>
</turboFilter>
<appender name="FILTERED"
class="ch.qos.logback.core.rolling.RollingFileAppender">
...
</appender>
<appender name="STDOUT"
class="ch.qos.logback.core.ConsoleAppender">
<layout class="ch.qos.logback.classic.PatternLayout">
<Pattern>TEST %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} -
%msg%n</Pattern>
</layout>
</appender>
<logger name="com.sample.legacy" additivity="false" level="warn">
<appender-ref ref="LEGACY"/>
</logger>
<logger name="com.sample.project" level="warn"> <!-- Add additivity="false"
if you don't want these also logged to STDOUT -->
<appender-ref ref="FILTERED"./>
</logger>
<root level="warn" >
<appender-ref ref="STDOUT" />
</root>
</configuration>
Ralph
On Dec 14, 2011, at 3:50 PM, Chris Pratt wrote:
> You might look at using the User Name as a Marker. Then you could set up a
> filter that will filter on that User's Marker.
> (*Chris*)
>
> On Wed, Dec 14, 2011 at 3:27 PM, Y M <[email protected]> wrote:
> Hello,
>
> I'm trying to obtain a certain logging configuration, but so far I'm
> unsuccessful. I've read through the Logback manual, but I don't know if I can
> do what I want.
>
> It is a web application, and my objective is to enable a finer logging level
> for specific users, getting written to a specific log file, allowing better
> debugging directly in production environment. When needed, someone will set a
> tuned XML config using JMX to enable logging for the duration of the
> tests/data gathering (JMX is working fine). This is the relevant part of my
> logback.xml file:
>
> <configuration debug="true">
>
> ...
>
> <appender name="FILTERED"
> class="ch.qos.logback.core.rolling.RollingFileAppender">
> <filter class="com.sample.project.UserFilter">
> <!--
> //filter code
> if (level != null &&
> !event.getLevel().isGreaterOrEqual(level)) {
> return FilterReply.DENY;
> }
> if (user.equals(MDC.get("userId"))) {
> return FilterReply.ACCEPT;
> } else {
> return FilterReply.DENY;
> }
>
> -->
> <level>DEBUG</level>
> <user>123456</user>
> </filter>
>
> ...
> </appender>
>
> <logger name="com.sample.project">
> <appender-ref ref="FILTERED" />
> </logger>
> <logger name="com.sample.legacy" additivity="false">
> <appender-ref ref="LEGACY" />
> </logger>
> <root level="WARN">
> <appender-ref ref="STANDARD" />
> </root>
>
> </configuration>
>
> With this config, I intend to have:
> - WARN+ level at root;
> - events from legacy project tree only on 'LEGACY' (working fine);
> - 'FILTERED' logging only DEBUG+ events from user '123456' under
> 'com.sample.project', while its level ramains at WARN (not OK).
>
> Sample:
> getLogger("com.sample.abc").warn("..."); //logged to STANDARD
> getLogger("com.sample.abc").debug("..."); //not logged
> getLogger("com.sample.legacy").warn("..."); //logged to LEGACY
> getLogger("com.sample.project").warn("..."); //logged to STANDARD; also
> logged to FILTERED if user is 123456
> getLogger("com.sample.project").debug("..."); //logged to FILTERED if user is
> 123456
>
> As I tested, a 'logger.debug()' from the desired user does not get logged,
> the filter is not even called, and I suspect that the effective WARN level
> denies the event before reaching my filter (I hoped for the other way
> around). If I set DEBUG on 'com.sample.project', 'FILTERED' will get the
> correct logging, but 'STANDARD' will be flooded with DEBUG+ logging from
> 'com.sample.project'. And disabling additivity on it removes all logging
> belonging to this hierarchy from 'STANDARD'.
>
> So, I see Logback is working properly, my desired logging seems to be against
> the standard architecture. But is there a way to archive the described effect?
> I was thinking of a TurboFilter, allowing lower level events from selected
> users (not tested yet), but I'm not sure the effective level would kick in
> first, also it wouldn't do the desired logging separation between 'STANDARD'
> and 'FILTERED' anyway. As another approach, maybe this would require a custom
> Logger class, handling specific appenders in a special way. Unfortunately, I
> have no idea if I can plug in custom Loggers, and also not sure how to code
> it (Logger class source is quite complex in a quick look).
>
> Sorry if it wasn't clear, I'm not sure how to present the situation. I can
> provide further details, if needed.
> Any help is welcome. If someone could show me which way to follow, maybe
> classes or methods to extend, I'd be grateful.
>
> Many thanks!
>
> _______________________________________________
> Logback-user mailing list
> [email protected]
> http://mailman.qos.ch/mailman/listinfo/logback-user
>
> _______________________________________________
> Logback-user mailing list
> [email protected]
> http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________
Logback-user mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-user
