WARNING: Version 5.0 of Kibana has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Configuring Kibana
editConfiguring Kibana
editThe Kibana server reads properties from the kibana.yml
file on startup. The default settings configure Kibana to run
on localhost:5601
. To change the host or port number, or connect to Elasticsearch running on a different machine,
you’ll need to update your kibana.yml
file. You can also enable SSL and set a variety of other options.
Table 1. Kibana Configuration Settings
|
Default: 5601 Kibana is served by a back end server. This setting specifies the port to use. |
|
Default: "localhost" This setting specifies the host of the back end server. |
|
Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects
the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests
to Kibana. This setting cannot end in a slash ( |
|
Default: 1048576 The maximum payload size in bytes for incoming server requests. |
|
Default: "your-hostname" A human-readable display name that identifies this Kibana instance. |
|
Default: "/app/kibana" This setting specifies the default route when opening Kibana. You can use this setting to modify the landing page when opening Kibana. |
|
Default: "http://localhost:9200" The URL of the Elasticsearch instance to use for all your queries. |
|
Default: true When this setting’s value is true Kibana uses the hostname specified in
the |
|
Default: ".kibana" Kibana uses an index in Elasticsearch to store saved searches, visualizations and dashboards. Kibana creates a new index if the index doesn’t already exist. |
|
Default: "discover" The default application to load. |
Default: |
|
|
Default: 1 The minimum zoom level. |
|
Default: 10 The maximum zoom level. |
|
Default: |
|
An array of subdomains used by the tile service.
Specify the position of the subdomain the URL with the token |
|
If your Elasticsearch is protected with basic authentication, these settings provide the username and password that the Kibana server uses to perform maintenance on the Kibana index at startup. Your Kibana users still need to authenticate with Elasticsearch, which is proxied through the Kibana server. |
|
Paths to the PEM-format SSL certificate and SSL key files, respectively. These files enable SSL for outgoing requests from the Kibana server to the browser. |
|
Optional settings that provide the paths to the PEM-format SSL certificate and key files. These files validate that your Elasticsearch backend uses the same key files. |
|
Optional setting that enables you to specify a path to the PEM file for the certificate authority for your Elasticsearch instance. |
|
Default: true To disregard the validity of SSL certificates, change this setting’s value
to |
|
Default: the value of the |
|
Default: 30000 Time in milliseconds to wait for responses from the back end or Elasticsearch. This value must be a positive integer. |
|
Default: |
|
Default: |
|
Default: 0 Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable. |
|
Default: 5000 Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying. |
|
Specifies the path where Kibana creates the process ID file. |
|
Default: |
|
Default: false Set the value of this setting to |
|
Default: false Set the value of this setting to |
|
Default: false Set the value of this setting to |
|
Default: 5000 Set the interval in milliseconds to sample system and process performance metrics. The minimum value is 100. |
|
Default: false If authentication is enabled, setting this to |
|
Default: true Set to false to disable Console. Toggling this will cause the server to regenerate assets on the next startup, which may cause a delay before pages start being served. |
|
Default: |
|
A list of configuration options that are based on the proxy target. Use this to set custom timeouts or SSL settings for specific hosts. This is done by defining a set of The valid match keys are |