Re: Logging: home-grown mechanism or syslog/event-log?

John Peacock wrote:

> 3) syslog uses a "threat" model for log levels, as opposed to a
> "functional" model. By this I mean that typically you normally have
> to set the log level high enough to capture the information you want
> and exclude the mass of detail which isn't important in normal
> operation. Unfortunately, since they set the LOG_XXX levels assuming
> that you were interested in only how _bad_ things are, not considering
> that sometimes you might want to log good things.

On the other hand, this is exactly what you want do for audit trails
with is what the access log idea is about. Debug traces are a different
beast and require different filtering, as you note above.

One more reason to completely separate operation logging and execution
tracing.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 20 17:43:20 2005