New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Logging configuration migration Configure security in Kibana »
Elastic Docs ›Kibana Guide [7.17] ›Set up ›Logging configuration migration

Logging configuration via CLI

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Logging configuration via CLI

edit

As is the case for any of Kibana’s config settings, you can specify your logging configuration via the CLI. For convenience, the --verbose and --silent flags exist as shortcuts and will continue to be supported beyond v7.

If you wish to override these flags, you can always do so by passing your preferred logging configuration directly to the CLI. For example, if Kibana has the following configuration in the kibana.yml, you can override the log level with CLI arguments, provided the full logging configuration is passed:

logging:
  appenders:
    custom:
      type: console
      layout:
        type: pattern
        pattern: "[%date][%level] %message"
    root:
      appenders: [default, custom]
      level: warn

You can override the flags with:

legacy logging Kibana Platform logging cli shortcuts

--verbose

--logging.root.level=debug --logging.root.appenders[0]=default --logging.root.appenders[1]=custom

--verbose

--quiet

--logging.root.level=error --logging.root.appenders[0]=default --logging.root.appenders[1]=custom

not supported

--silent

--logging.root.level=off

--silent

To preserve backwards compatibility, you are required to pass the root default appender until the legacy logging system is removed in v8.0.

« Logging configuration migration Configure security in Kibana »
Was this helpful?
Feedback