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

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.
  • by Lecar_red (5694) on 2006.02.06 13:02 (#46028) Journal

    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 was very straight forward to add custom logging appender. (the thing that does the actually logging). In my case, I added one to make special sub directories for logfiles under certain conditions making it easier to debug.

    To be honest, I didn't really look to much at Log::Dispatch and don't know much about it.

    Also, MikeS is really great at providing help (on the mailing list) and fixing issues. (thanks Mike)