Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

sigzero (5768)

sigzero
  (email not shown publicly)

I am the proverbial "accidental" programmer. I have found that I really like Perl and programming so I am pursuing that route now. I am the Debian systems administrator and junior Perl programmer for a company called Inspire.

Journal of sigzero (5768)

Monday February 06, 2006
11:40 AM

Log::Dispatch vs Log4perl?

[ #28594 ]
Which do you use and why? The both attempt to be the "one stop shop" for logging.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I choose log4perl for two main reasons:

    • We have ops folks and it's logging configuration seemed to be most friendly to ops folks, especially those already accustomed to log4j.
    • It is very flexible. It was very easy to add custom format values (MDC is the log4perl term). For example, in a web application the session id was added as a MDC value for all logging that was part of the a request across all internal components. This made it much easier to debug web request across multiple modules. Also, it w
  • Log4perl lets you have your cake and eat it - you can use log4j configurations and use Log::Dispatch dispatchers.

    There is a very good article at perl.com [perl.com]

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
  • I've used Log::Dispatch for a long time and looked into switching to Log4perl. Both seemed fine for my needs.

    The main reason I didn't switch at the time was because I realized that Log4perl's config required too much knowledge of the app's internals (e.g. class layout, I think) for our admins to alter. It's probably more of an admin problem than a Log4perl problem. Since I needed to write a simpler config front-end for it anyway there seemed little reason for me to use one over the other. I stuck with w

    • The main reason I didn't switch at the time was because I realized that Log4perl's config required too much knowledge of the app's internals (e.g. class layout, I think)

      Actually, that's up for you to decide.

      To enable logging in particular areas of an application, you can use the class structure. But that's just a feature and not required at all.

      Instead, you can just enable/disable logging of the overall application or choose entirely different categories (i.e. make up your own hierarchy). The class