fine-grained logging

Current logging configuration is just one bit: verbosity on/off. This makes it hard to monitor and debug large instances.

Let's collect ideas for improvement in this ticket:

• per-request logging - ability to run single request with verbose logging is very handy for debugging. We have a prototype in /trace endpoint in HTTP module but this module does not log everything for a given request, and also it should be much easier to use than full HTTP.
• per-type logging - it might be handy to enable/disable certain types of logging, e.g. control socket log might be too noisy if there is enough API traffic etc.
• fine grained log levels exposed to the logging system - external log collectors need to know if given message is debug/info/error etc.
• structured logging? log some rudimentary metadata in structured form - e.g. query name + type + rcode? This might be very handy for network operations centers etc.

added feature usability labels

mentioned in issue #528 (closed)

The exposed log levels should correspond with syslog (see man syslog.3). These can be effectively filtered by using journalctl -p (see man journalctl.1) when running under systemd.

The journalctl log levels should be supported out of the box by default, since that's the main supported way to run kresd.

added 1 deleted label

mentioned in issue #495 (closed)

mentioned in issue #207

mentioned in issue #537

It's possible to turn on per-request verbose logging using policy.DEBUG_IF or policy.DEBUG_CACHE_MISS.

marked the checklist item per-request logging - ability to run single request with verbose logging is very handy for debugging. We have a prototype in /trace endpoint in HTTP module but this module does not log everything for a given request, and also it should be much easier to use than full HTTP. as completed

assigned to @tkrizek

assigned to @ljezek and unassigned @tkrizek

mentioned in merge request !1181 (merged)

marked the checklist item per-type logging - it might be handy to enable/disable certain types of logging, e.g. control socket log might be too noisy if there is enough API traffic etc. as completed

marked the checklist item fine grained log levels exposed to the logging system - external log collectors need to know if given message is debug/info/error etc. as completed

closed