use Perl

• Log4perl (Score:1)

  by Lecar_red (5694)

  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
• have your cake and eat it with log4perl (Score:2)

  by TeeJay (2309)

  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;
• Both work fine (Score:1)

  by bluto (225)

  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
  • Re:Both work fine (Score:1)

    by Perlmeister (6689)

    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