Logging beats a debugger if you want to know what's going on in your code during runtime. However, traditional logging packages are too static and generate a flood of log messages in your log files that won't help you.

Log::Log4perl is different. It allows you to control the amount of logging messages generated very effectively. You can bump up the logging level of certain components in your software, using powerful inheritance techniques. You can redirect the additional logging messages to an entirely different output (append to a file, send by email etc.) -- and everything without modifying a single line of source code.

NEW:
Collaborate with Log4perl on Github!

• Get started with the tutorial.
• Check the documentation.
• Get the latest source from github.com:
    git clone git@github.com:mschilli/log4perl.git
  
• Search an archive of old messages
• Go to the Github project page

Further reading

• Using Catalyst with Log4perl
• Horshack's Log4perl Page
• Apache Logging Services
• log4j Homepage (original)
• log4j Homepage (new gen)
• And here's another article: Don't Use System.out.println! Use log4j

CPAN Modules already using Log::Log4perl:

Slides for Mike's talk at OSCON 2008.

02/20/2017:
Released version 1.49

06/25/2007:
Talk at YAPC 2007 (Houston, TX):
Smart Logging with Log4perl.

Get your Log::Log4perl T-Shirt:

09/12/2002:

Retire your debugger, log smartly with Log::Log4perl! -- Mike's article on logging with Log::Log4perl on perl.com. Errata for this article.

---

Documentation:

Manual
Frequently Asked Questions
Changes

---

Download:

CPAN:
Log-Log4perl

Stable Release (02/20/2017) Log-Log4perl-1.49.tar.gz

Installation on Unix:
It's a regular Perl module installation procedure, use the CPAN shell for convenience: perl -MCPAN -e'install Log::Log4perl'

Installation on Win32:
We're providing a PPM package: Windows installation instructions.

---

Contact:

Please send bugs reports or requests for enhancements to the authors via our mailing list: log4perl-devel@lists.sourceforge.net

Subscribe to the mailing list. Or, browse the log4perl-devel mailing list archive. Or, use a better indexed archive of newer messages (2007-...).