From: Oleg Babin <olegrok@tarantool.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>,
tml <tarantool-patches@dev.tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v3 00/10] lua/log: add an ability to setup logger without box.cfg{}
Date: Wed, 27 May 2020 15:58:03 +0300 [thread overview]
Message-ID: <02822615-4b8e-e90e-b990-27dee3237a32@tarantool.org> (raw)
In-Reply-To: <20200527111406.145422-1-gorcunov@gmail.com>
Hi! Thanks for your changes.
I think that it's a bit redundant to have "log" prefixes for log.cfg
options.
log.cfg({format = ..., level = ..., non_block = ...}) looks better IMO.
Also it's still possible to setup invalid value for log_level.
```
tarantool> log.cfg{log_format = 'invalid'}
---
- error: 'builtin/log.lua:239: log: ''log_format'' must be json,plain'
...
tarantool> log.cfg{log_level = -1}
---
...
tarantool> log.cfg
---
- log_format: json
log_level: -1
log_nonblock: false
...
```
Also I have several comments for specific commits. I'll send them
separately.
On 27/05/2020 14:13, Cyrill Gorcunov wrote:
> In the series we add an ability to configure logger early
> without calling box.cfg{}. The syntax is the same as
> in box.cfg{} call.
>
> There was an idea to implement something similar via triggers but
> I think this will require a way more efforts and code redesign,
> so at first lets stick to simplier solution.
>
> v2 by Oleg:
> - hide box_api symbols from users
> - initialize logger via log.cfg() call to look similar to box.cfg
> v3 by Oleg:
> - add parametesr verification
> - allow to reconfig via log.cfg() call
>
> branch gorcunov/gh-689-logger-3
> issue https://github.com/tarantool/tarantool/issues/689
>
> Cyrill Gorcunov (10):
> core/say: drop redundant declarations
> core/say: drop vsay declaration
> core/say: do not reconfig early set up logger
> lua/log: declare say_logger_init and say_logger_initialized
> lua/log: put string constants to map
> lua/log: do not allow to set json for boot logger
> lua/log: declare log as separate variable
> lua/log: use log module settings inside box.cfg
> lua/log: allow to configure logging without a box
> test: use direct log module
>
> src/box/lua/load_cfg.lua | 24 +++-
> src/lib/core/say.c | 18 ++-
> src/lib/core/say.h | 8 +-
> src/lua/log.lua | 216 +++++++++++++++++++++++++++++++----
> test/app-tap/logger.test.lua | 28 ++++-
> 5 files changed, 255 insertions(+), 39 deletions(-)
>
prev parent reply other threads:[~2020-05-27 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 11:13 Cyrill Gorcunov
2020-05-27 11:13 ` [Tarantool-patches] [PATCH v3 01/10] core/say: drop redundant declarations Cyrill Gorcunov
2020-05-28 7:21 ` Kirill Yukhin
2020-05-27 11:13 ` [Tarantool-patches] [PATCH v3 02/10] core/say: drop vsay declaration Cyrill Gorcunov
2020-05-28 7:21 ` Kirill Yukhin
2020-05-27 11:13 ` [Tarantool-patches] [PATCH v3 03/10] core/say: do not reconfig early set up logger Cyrill Gorcunov
2020-05-27 11:14 ` [Tarantool-patches] [PATCH v3 04/10] lua/log: declare say_logger_init and say_logger_initialized Cyrill Gorcunov
2020-05-27 11:14 ` [Tarantool-patches] [PATCH v3 05/10] lua/log: put string constants to map Cyrill Gorcunov
2020-05-27 12:58 ` Oleg Babin
2020-05-27 11:14 ` [Tarantool-patches] [PATCH v3 06/10] lua/log: do not allow to set json for boot logger Cyrill Gorcunov
2020-05-27 11:14 ` [Tarantool-patches] [PATCH v3 07/10] lua/log: declare log as separate variable Cyrill Gorcunov
2020-05-27 12:58 ` Oleg Babin
2020-05-27 11:14 ` [Tarantool-patches] [PATCH v3 08/10] lua/log: use log module settings inside box.cfg Cyrill Gorcunov
2020-05-27 11:14 ` [Tarantool-patches] [PATCH v3 09/10] lua/log: allow to configure logging without a box Cyrill Gorcunov
2020-05-27 12:59 ` Oleg Babin
2020-05-27 11:14 ` [Tarantool-patches] [PATCH v3 10/10] test: use direct log module Cyrill Gorcunov
2020-05-27 12:59 ` Oleg Babin
2020-05-27 12:58 ` Oleg Babin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02822615-4b8e-e90e-b990-27dee3237a32@tarantool.org \
--to=olegrok@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v3 00/10] lua/log: add an ability to setup logger without box.cfg{}' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox