[bind10-dev] Enabling/disabling logging on per-message basis

[Michal 'vorner' Vaner]

Hello

On Wed, Feb 29, 2012 at 09:07:05AM -0800, Jerry Scharf wrote:
> I am not sure that enabling/disabling is the right right way to see 
> this. You will always have some system default level of logging in 
> operation. It is more a question of whether a single query can get a 
> different logging level and processing than the normal production stream.

The per-query logging is indeed very nice idea and I'm for implementing it.
However, it is a completely different and orthogonal idea. To do the per-query
thing, we'd create a new logger for the query and it would log there, so you
could define different levels of debugging on different queries. But that would
be also a lot more work than what I propose (I'd like to have both these
features).

Maybe enabling/disabling is not the right word. But I want to be able to
override the logging level for some messages, like say I want INFO with the
exception of this debug message, which should be logged as well. As I said, I
believed this would be almost for free, at least when no overrides are
configured (and some log n would be paid for n overridden messages). But if you
think this would involve too much overhead, I think doing an experiment and
measuring how much it slows things down would be a really easy task.

With regards

-- 
I have a theory that it's impossible to prove anything, but I can't prove it.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20120301/fa234007/attachment.bin>