Loading

Kibana logging

ECE ECK Elastic Cloud Hosted Self Managed

You do not need to configure any additional settings to use the logging features in Kibana. Logging is enabled by default.

In all deployment types, you might want to change the log level for Kibana. In a self-managed, ECE, or ECK deployment, you might want to further customize your logging settings to define where log messages are displayed, stored, and formatted, or provide granular settings for different loggers.

You can also configure Kibana task manager health monitoring using logging settings.

Tip

For additional information about the available logging settings, refer to the Kibana configuration reference.

The way that you access your logs differs depending on your deployment method.

Access your logs using one of the following options:

If you run Kibana as a service, the default location of the logs varies based on your platform and installation method:

On Docker, log messages go to the console and are handled by the configured Docker logging driver. To access logs, run docker logs.

For Debian and RPM installations, Elasticsearch writes logs to /var/log/kibana.

For macOS and Linux .tar.gz installations, Elasticsearch writes logs to $KIBANA_HOME/logs.

Files in $KIBANA_HOME risk deletion during an upgrade. In production, you should configure a different location for your logs.

For Windows .zip installations, Elasticsearch writes logs to %KIBANA_HOME%\logs.

Files in %KIBANA_HOME% risk deletion during an upgrade. In production, you should configure a different location for your logs.

If you run Kibana from the command line, Elasticsearch prints logs to the standard output (stdout).

You can also consume logs using stack monitoring.