Re: [Openinteract-dev] what to log and when

[Chris W. <ch...@cw...>]

Perrin Harkins said:
> Most admins will tell you they don't want to hear about it unless they
> need to do something about it, and most developers will tell you they
> take out their debugging stuff when they find the bug, so my advice is
> to have very minimal logging in general.  Excessive attention to logging
> is usually a sign of trouble in my opinion.

I agree with you on administrators. And the error browser + files is
mainly intended for them.

But regarding developers I think there are differences between good
logging messages and the quick-iteration debugging messages ("got here",
data structure dumps) that usually take the place of the debugger.
log4perl makes it awfully easy to assign different logging levels to
different logging categories; combined with a consistent logging strategy
for a framework people can peer into the innards of what's going on in a
particular area of the system. I compare it to turning on DBI's trace
functionality. IMO this is extremely useful -- moreso because it's
externally configurable.

The trick is to get the logging at least roughly consistent, otherwise
you'll get too little/too much whenever you change a logging level.

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.