The stupid question is the question not asked | |
PerlMonks |
Re: Defensive Programming and Audit Trailsby cybear (Monk) |
on Aug 06, 2002 at 13:01 UTC ( [id://188006]=note: print w/replies, xml ) | Need Help?? |
Dispite the barely obfuscated obsenity for a name, FoxtrotUniform
is right on! I have been working in Operations/Support for seven years, and I have found that the vast majority of programs out there couldn't log their way out of a saw mill. Think Windoze "some.dll has caused a fault in module some.dll"... really freeking helpful! NOT! A good program should log every pertinant piece of information,
For example, this is the log of an FTP program that I wrote:
In this case, the general log (above) is archived and kept for 120 days, the detailedLog, FTP Debuging (Level 1) information, is kept in a seperate file and archived for 30 days. This keeps the general log more "user friendly" but still captures the truley "nitty-gritty" incase of programming errors. Scanning through this file for errors is easy, visually the
Additionally successful downloads are marked with a "+",
In Section
Meditations
|
|