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.

Solid programs III 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Years back I implemented a circular queue error log, which would keep n messages in memory and dump the log to disk on error. The advantage of having the log in memory was that it would still be displayable if the application dumped core. (Ah, the joys of working in C...)

    We logged each user "gesture" (entered "foo" in the bar field, clicked OK, etc.), which gave us a trail of breadcrumbs to follow to repeat the failure, though in practice we rarely had to look back more than a dozen entries from the end o

  • It is for the implementation of this type of level logging that I use Log::Log4perl [cpan.org] - This module incorporates a very flexible category and class logging system which allows for differing log actions to be defined based upon the class and level of the invoking log message. These actions include logging to DBI handle, email, file, syslog or screen.

    If does not currently incorporate the type of contextual logging which you seek, but would form an excellent base from which to build an alternate logging platfo

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.