in reply to Re: Re: Determining debug levels
in thread Determining debug levels

In these days of cheap disk space, freely available filtering languages like our beloved Perl, and fast editors with good search commands, selective logging of warnings and errors is almost certainly the wrong choice. Remember, you can always filter downstream, but if valuable information is ignored, you will never get it back.

That's a good point. Big logs are much less of a problem that in bygone days.

Still, if you go this way, be sure to do a back-of-the-envelope calculation to guestimate how much disk space your logs will grow per day. You'll also want to have some sort of log aging scheme. Having a system roll over in the field because the disk filled up can be embarrassing, especially when everyone claims it can't happen.

Replies are listed 'Best First'.
Re: Re: Re: Re: Determining debug levels
by clemburg (Curate) on Feb 28, 2002 at 10:56 UTC

    Log aging scheme - that was the word I was looking for (this was the "etc." free features in my previous post about logging to a database). One point more for the database side. Note that most database systems have monitoring tools that will alert you to conditions like database filling up. Also, usually a well-thought out aging/backup scheme is applied to databases used for real applications, so you get that for free, too.

    Christian Lemburg
    Brainbench MVP for Perl
    http://www.brainbench.com

[reply]

In Section Seekers of Perl Wisdom