0xDECAFBAD

It's all spinning wheels and self-doubt until the first pot of coffee.

Yes, Virginia, there is a Log4Perl.

Log::Log4perl is different. It is a pure Perl port of the widely popular Apache/Jakarta log4j library for Java, a project made public in 1999, which has been actively supported and enhanced by a team around head honcho Ceki Gülcü during the years.

The comforting facts about log4j are that it's really well thought out, it's the alternative logging standard for Java and it's been in use for years with numerous projects. If you don't like Java, then don't worry, you're not alone -- the Log::Log4perl authors (yours truly among them) are all Perl hardliners who made sure Log::Log4perl is real Perl.

Source:perl.com: Retire your debugger, log smartly with Log::Log4perl! .

Wow, I hadn't noticed this before. We've been looking for a Log4J-workalike in for our perl-based web apps at work, and thought CPAN:Log::Agent was where it's at - and it still may be - but CPAN:Log::Log4Perl looks very keen now.

shortname=ooodoa

Archived Comments

  • kellan
    We've been having really good luck with Log::Log4perl on a couple of medium to large projects. Lots and lots of flexibility, easy to get started, and being built on top of amazing Log::Dispatch hierarchy was a stroke of genius that opens up lots of resources. Can't wait until I have an excusre to use the fact that it can parse log4j config files transparently.
  • mark
    I've been using Log4perl as well, as a means of getitng common logging between our Perl and Java code bases. It works really well, other than the fact that not all the layout formatting codes are yet implemented. But with a little care, it's easily possible to have your Perl apps logging to the same places as your Java or J2EE based applications, which really improves the ability to debug and analyze systems which use both....