Alexander Turenko

> NO_DOC=internal > NO_CHANGELOG=internal It fixes a user visible problem, how it can be internal?

Reading for inspiration: https://www.python.org/dev/peps/pep-0282/ https://docs.python.org/3/library/logging.html http://logback.qos.ch/manual/architecture.html

Points to don't forget: * A code that uses logger and want to support hot reload should work gracefully. It seems, we can just make loggers be singletons or kinda:...

Not everything within one issue :) We'll consider other logger improvements, but, please, file another issue regarding MDC. If you'll mark it with the [logger](https://github.com/tarantool/tarantool/issues?q=is%3Aissue+is%3Aopen+label%3Alogger) label, we'll not miss it....

I guess we want to use the hierarical logger in general purpose modules, so an application developer or an administrator may choose how verbose logs should be for different components...

@AnastasMIPT Are you working on the task? I'll reassign it to your team so (and will exclude from my team's list of candidates for next tasks). Please, let me know...

I'm against of autodetermination of a 'module name': 1. Author of a module have no control how its module is named from logger perspective. 2. What name should be issued...

I agree with @R-omk, we should not do any sometimes-work automatic logger name determination, we should not introduce concept of the 'module' as replacement for logger name. I already wrote...

What is 'multiple require override problem'? Can you describe it in terms of a behaviour of a user code? IOW, show an example, its expected behaviour and its actual behaviour...

It is known flaw of marshalling between msgpack and Lua. There is an idea to take the space format into consideration on the marshalling: #5933. I hope sooner or later...