Bug #94492 for Dancer-Logger-Log4perl: RFE: Add a Log4perl category for sectioning off Dancer logging

Sun Apr 06 20:40:59 2014 colink [...] perlDreamer.com - Ticket created

Subject:

RFE: Add a Log4perl category for sectioning off Dancer logging

It's not a bug, it's a request for a new feature. Right now, Dancer::Logger::Log4perl uses the root logger, which means when you're trying to get INFO or DEBUG from your own code, you also get all everything from Dancer at the same time. It would be nice if Dancer::Logger::Log4perl used the "Dancer" category for its logging. If that config was missing from the Log4perl config file, then it would default back to the root logger and all current behavior would be unaffected. But if it was defined, then it could be varied independently from other sections of the code.

Mon May 05 10:24:21 2014 CASAO [...] cpan.org - Correspondence added

I have just uploaded a new version (0.9.0) which should resolve this.

Mon May 05 10:24:21 2014 The RT System itself - Status changed from 'new' to 'open'

Thu May 08 14:07:05 2014 colink [...] perlDreamer.com - Correspondence added

From:

colink [...] perlDreamer.com

This does indeed give more flexibility, but it seems to ignore the config settings for layout. I'll attach some sample log files from t/02-full.t I'm not familiar with Dancer's logging internals, but I was thinking something simple like specifying a category to the logger might work: $self->{logger} = $class->get_logger( Dancer::Config::setting('log') );

Subject:

02-full.t.log.0.9.0

Download 02-full.t.log.0.9.0
application/octet-stream 7.2k

Message body not shown because it is not plain text.

Subject:

02-full.t.log.0.8.1

Download 02-full.t.log.0.8.1
application/octet-stream 2.4k

Message body not shown because it is not plain text.