Hi Jake.
Thank you for explaining this very well. My motivation for having two
separate appenders that need to be tuned independently this way, is that I
need one log file/appender for debugging/analyzing and one for monitoring.
- The debugging log can in some periods be very verbose when doing
de
Gary,
Thanks for this - it will be very, very useful for our project.
Ed
On Wed, Oct 2, 2013 at 7:53 AM, Gary Gregory wrote:
> On Tue, Oct 1, 2013 at 1:08 PM, Gary Gregory wrote:
>
>> I create a JIRA to track possible solutions:
>> https://issues.apache.org/jira/browse/LOG4J2-415
>>
>> I have
Apply appenderA and AppenderB to the root logger. I always set the root
logger level to WARN to avoid trace/debug/info messages from arbitrary
libraries.
Then, if you want INFO logging for most of your library, configure the lowest
common denominator package for your app, let's say "com.mya
On Tue, Oct 1, 2013 at 1:08 PM, Gary Gregory wrote:
> I create a JIRA to track possible solutions:
> https://issues.apache.org/jira/browse/LOG4J2-415
>
> I have attached two different solutions in a patch file.
>
I reworked the code in the date converter solution to be more OO. This is
now in SV
Hi.
No, I do not want to exclude the more severe logging levels, but I want to
enable more verbose logging for specific classes for appender A
independently of appender Bs logging of those same classes, and vice versa:
Appender A and B is defined.
Appender A is logging INFO+ for all by default, w
By default, if you set the level of a logger/appender to debug, it will
process debug, info, warn, error and fatal messages.
Is this what you want, or do you want to include only debug-level messages,
and exclude info, warn, error and fatal messages?
On Wednesday, October 2, 2013, fedinho wrote:
