Re: User-based logger level

In Log4j 2 the DynamicThresholdFilter can be specified a) globally (equivalent to Logback's TurboFilter) b) on a Logger c) in the Appender Reference in a Logger and d) on an Appender. For your use case you could specify the DynamicThresholdFilter on each Logger and you would get the effect you

Re: User-based logger level

Thanks for all the nice replies. It's a good starting point for me. We may need a bit more than out-of-the-box MDCFilter or DynamicThresholdFilter, in that for different ejbs different users get the DEBUG level. For example, for ejb1, user A gets DEBUG while user B gets WARNING; for ejb2, user

File rolling in log4j extras

Hi all, I am using log4j extras for archiving the log files by fixed window rolling policy. But the log files inside the archiving do not change their names after rolling over though outer achieve is rolling fine. It is like: mylog.1.log.zip has mylog.1.log and mylog.2.log.zip also has mylog.1.log.

Re: User-based logger level

In log4j 2.x there are tons of filters which might help here: http://loggingtest.apache.org/log4j/2.x/manual/filters.html (temporary domain) Cheers Christian On Mon, Jun 11, 2012 at 5:28 PM, Jacob Kjome wrote: > > It's possible that Log4j2 supports this out of the box, but for Log4j1, the > obvi

Re: User-based logger level

Yours is a text-book requirement: http://logback.qos.ch/reasonsToSwitch.html#filters See the docs on MDCFilter at [1]. [1] http://logback.qos.ch/manual/filters.html#TurboFilter -- Ceki http://twitter.com/#!/ceki On 11.06.2012 11:55, yong...@agfa.com wrote: Dear all, We're about to implem

Re: User-based logger level

It's possible that Log4j2 supports this out of the box, but for Log4j1, the obvious way is to call logger.log() methods that accept an explicit Level/Priority [1].  Set a ThreadLocal with the Level to use and pass that Level to log() method. [1] http://logging.apache.org/log4j/1.2/apidocs/o

User-based logger level

Dear all, We're about to implement a logging strategy that for different users different effective logger level are used. In particular, we are doing EJB, and we have already pushed user info onto MDC to implement this strategy. By default, the system will run using the following example logg

Re: class specific logging level

So, I found out the why RollingFileAppender wasn't behaving like ConsoleAppender. Because I had mentioned a threshold level in RollingFileAppender but not in ConsoleAppender. Removing threshold tag from RollingFileAppender worked. aggarwal wrote: > > I think I have found the solution to my prob