Consume logging config via CLI

[mshustov]

Kibana supports 4 logging settings being passed via CLI

kibana/src/cli/serve/serve.js

Lines 136 to 139 in 4e8ab56

	if (opts.quiet) set('logging.quiet', true);
	if (opts.silent) set('logging.silent', true);
	if (opts.verbose) set('logging.verbose', true);
	if (opts.logFile) set('logging.dest', opts.logFile);

.
We can support at least logging.root.level that supersedes quiet, silent and verbose.

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[TinaHeiligers]

We can support at least logging.root.level that supersedes quiet, silent and verbose.

@restrry what is the scope of this issue? The words: "...at least..." make me think that it might be larger than just adding support for logging.root.level.

ATM, we only get KP logs from kibana not running in dev mode when we add the full config for the root level logger:

node scripts/kibana serve --logging.root.level=debug --logging.root.appenders[0]=default --logging.root.appenders[1]=console

Without --logging.root.appenders[1]=console, only the legacy logs show up.

If we did introduce a shortcut for the root level logger, what would this look like? (something along the lines of --logging.level=debug or --logging=debug?

Would we then require the appenders to be passed in too (and throw an error if they aren't) or would we proactively add the other config settings? For example, internally set the root appenders to default and console?

Once we remove the legacy logging system, we should be able to introduce cleaner shortcuts (or repurpose the ones folks are already used to using). Until then though, how about just adding support for the full config path as it would be set in the config yml file?

[mshustov]

If we did introduce a shortcut for the root level logger, what would this look like?

No, I wouldn't introduce the shortcuts.

If it already works, I'd add a note to the logging/README.md on how to reproduce the legacy system behavior (for both CLI and config).
Something like:

Logging configuration via CLI

legacy logging	Kibana Platform logging
--verbose	--logging.root.level=debug --logging.root.appenders[0]=default --logging.root.appenders[1]=console
....	...

*note that you have to pass the default appender until the legacy logging system is removed in v8.0

ATM, we only get KP logs from kibana not running in dev mode when we add the full config for the root level logger:

Do you mean that a user running Kibana dist has to specify --logging.root.appenders to see Kibana Platform logs?

Until then though, how about just adding support for the full config path as it would be set in the config yml file?

Could you elaborate, please?

[TinaHeiligers]

Do you mean that a user running Kibana dist has to specify --logging.root.appenders to see Kibana Platform logs?

When I start kibana without adding any config to kibana.yml with any of

• node scripts/kibana serve,
• node scripts/kibana serve --logging.root.level=debug or
• scripts/kibana serve --logging.root.level=debug --logging.root.appenders[0]=default

I only get legacy platform logs.
So yes, the appenders have to be specified.

Until then though, how about just adding support for the full config path as it would be set in the config yml file?

Could you elaborate, please?

This was a follow up question for if we are going to introduce shortcuts. What I meant was using --logging.root.level=debug --logging.root.appenders[0]=default --logging.root.appenders[1]=console rather than taking over the --verbose option that we use for legacy logs (or some other shortcut that we would have used if we decided to introduce shortcuts).