[bind10-dev] Logging Requirements - Input Required

[Michal 'vorner' Vaner]

Hello

A had a short look at that. I think we might want to be able to pipe the
messages to a program (it is similar to named pipe, but it seems more convenient
if BoB would just start the program and it would go there all by itself, or it
would be started by some bind10-logger, or whatever).

And I think we might want two logging formats. One textual looking that an admin
can have a look at and one machine-parsable (JOSN? Some binary format?), so it
can be piped to a third-party filter program or formatter or something like that
(it would allow for much easier extending I think).


Another thing is, I understand DEBUG in most application as useful for
config-level debugging as well (when it doesn't do what I want, I turn some
lower level of debugging on and see what it really does inside and why is it
doing something else). Then after I debug the config, I turn debugging off and
let it run with normal log outputs. So I think that DEBUG should be readable for
admins as well, just that it would give far too much information to be used in
real life.

Another nice feature I saw somewhere (but that's probably too soon to think
about that) is something like:

| INFO 12:21 ComponentFoo Some message
| (Repeats 2342 times)

Because, sometimes, when something goes wrong, it might want to complain about
the same thing over and over again. Spamming is not good, it is hard to find the
useful info around it.

With regards

-- 
Fragile. Do not turn umop ap1sdn!

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