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

use Perl

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.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

More about instrumentation from Tom Kyte. (Score:1)

by rblackwe (5489)

More about instrumentation from Tom Kyte. http://tkyte.blogspot.com/2005/06/instrumentation.html [blogspot.com]
Just a Guess... (Score:2)

by Dom2 (2981)

I would hazard a guess that you could do something like this log4perl. You'd need to configure some appender to record the last (say) 100 log lines at debug, in memory, in a circular buffer. When the crash hits, mail them off.
-Dom
Another instrumentation class (Score:1)

by pemungkah (3)

NASA finally open-sourced an older version of the CGI stuff I worked on for them. I seem to remember a Perlier logging class in there somewhere that I should clean up and re-release.
Log everything, iterate your configs (Score:1)

by bluto (225)

I think the main problem with logging is that initially you don't really know what information will be useful so it's best to log much more than you think you will need. For me this also applies to the format of the logs -- I just don't know what will be the best format to delog when a problem does occur. For some apps it seems that certain types of logs (e.g. text) are just hard sift through, when for others those same types work great.
If you use something like log4perl or Log::Dispatch, as suggested ear