Tickets :: Comment on [#10773] Improve logging in Horde

* Your Email Address
* Spam protection	Enter the letters below: .__ . ..___ __ .___. [__)\| \|[__ / ` \| \| \|__\|[___\__. \|
Comment	>> I think the solution here is to implement Request 10805, and then >> when logging queries, log Stream resources as <Stream> rather than >> their contents. Any objections? > > Unfortunately, I don't think that solves this issue. Two major > problems jump out to me: > > 1. Someone can still pass in a multi-MB string. It is perfectly > valid. and will always remain valid, according to the API. This > solution maintains the status quo on this case. > 2. Logging as <Stream> now prevents us from EVER debugging the > contents of the data values. Just because it is a stream doesn't > mean we shouldn't log it (a stream could contain 1 byte of data). > > I still believe the solution needs to be a way of controlling the log > level at the DB package level, as opposed to the Log package level. > E.g. an option that can be passed to the Db library that allows three > levels of data logging: > > * ALL: Log all entries > * MAX_SIZE: Log all entries smaller than a certain size (1KB? > configurable?; use placeholders (e.g. "<Stream>", "<String>") > otherwise > * NEVER: Never log entries; always use placeholders
Attachment
Watch this ticket