---
title: General settings in Kibana
description: 
url: https://www.elastic.co/elastic/docs-builder/docs/3167/reference/kibana/configuration-reference/general-settings
products:
  - Kibana
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Self-managed Elastic deployments: Generally available
---

# General settings in Kibana
Use these settings to configure general features available in Kibana.

## General settings
<definitions>
  <definition term="console.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Toggling this causes the server to regenerate assets on the next startup, which may cause a delay before pages start being served. Set to `false` to disable Console.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="execution_context.enabled">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Propagate request-specific metadata to Elasticsearch server by way of the `x-opaque-id` header.
It is available in Elastic Cloud 8.1.0 and later versions.
Datatype: `bool`
  </definition>
  <definition term="newsfeed.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Controls whether to enable the newsfeed system for the Kibana UI notification center. Set to `false` to disable the newsfeed system.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="node.roles">
    <stack-availability>Elastic Stack: Preview</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Indicates which roles to configure the Kibana process with, which will effectively run Kibana in different modes. Valid options are `background_tasks` and `ui`, or `*` to select all roles.
Datatype: `string`
Default: `*`
  </definition>
  <definition term="notifications.connectors.default.email">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Choose the default email connector for user notifications. As of `8.6.0`, Kibana is shipping with a new notification mechanism that will send email notifications for various user actions, e.g. assigning a *Case* to a user. To enable notifications, an email connector must be [preconfigured](https://www.elastic.co/docs/reference/kibana/connectors-kibana/pre-configured-connectors) in the system via `kibana.yml`, and the notifications plugin must be configured to point to the ID of that connector.
Datatype: `string`
  </definition>
  <definition term="ops.interval">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set the interval in milliseconds to sample system and process performance metrics. The minimum value is 100.
Datatype: `int`
Default: `5000`
  </definition>
  <definition term="ops.cGroupOverrides.cpuPath">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Override for cgroup cpu path when mounted in a manner that is inconsistent with `/proc/self/cgroup`.
Datatype: `string`
  </definition>
  <definition term="ops.cGroupOverrides.cpuAcctPath">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Override for cgroup cpuacct path when mounted in a manner that is inconsistent with `/proc/self/cgroup`.
Datatype: `string`
  </definition>
  <definition term="path.data">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The path where Kibana stores persistent data not saved in Elasticsearch.
Datatype: `string`
Default: `data`
  </definition>
  <definition term="permissionsPolicy.report_to">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Permissions Policy `report-to` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy).
Datatype: `string`
  </definition>
  <definition term="pid.file">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Specifies the path where Kibana creates the process ID file.
Datatype: `string`
  </definition>
  <definition term="status.allowAnonymous">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

If authentication is enabled, setting this to `true` enables unauthenticated users to access the Kibana server status API and status page.
Datatype: `bool`
Default: `false`
  </definition>
</definitions>

## Content Security Policy (CSP) settings
<definitions>
  <definition term="csp.script_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `script-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src).
Datatype: `string`
  </definition>
  <definition term="csp.disableUnsafeEval">
    <stack-availability>Elastic Stack: Deprecated since 8.7</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this to `false` to add the [`unsafe-eval`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_eval_expressions) source expression to the `script-src` directive.
When `csp.disableUnsafeEval` is set to `true`, Kibana will use a custom version of the Handlebars template library. Handlebars is used in various locations in the Kibana frontend where custom templates can be supplied by the user when for instance setting up a visualisation. If you experience any issues rendering Handlebars templates, please set this setting to `false` and [open an issue](https://github.com/elastic/kibana/issues/new/choose) in the Kibana GitHub repository.
Datatype: `bool`
Default: `true`

<admonition title="Deprecation details">
  Deprecated in 8.7.0. Use `csp.script_src: ['unsafe-eval']` instead if you wish to enable `unsafe-eval`. This config option will have no effect in a future version.
</admonition>

  </definition>
  <definition term="csp.worker_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `worker-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/worker-src).
Datatype: `string`
  </definition>
  <definition term="csp.style_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `style-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/style-src).
Datatype: `string`
  </definition>
  <definition term="csp.connect_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `connect-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/connect-src).
Datatype: `string`
  </definition>
  <definition term="csp.default_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `default-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/default-src).
Datatype: `string`
  </definition>
  <definition term="csp.font_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `font-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/font-src).
Datatype: `string`
  </definition>
  <definition term="csp.frame_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `frame-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-src).
Datatype: `string`
  </definition>
  <definition term="csp.img_src">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `img-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/img-src).
Datatype: `string`
  </definition>
  <definition term="csp.object_src">
    <stack-availability>Elastic Stack: Generally available since 9.3</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `object-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/object-src).
Datatype: `string`
  </definition>
  <definition term="csp.frame_ancestors">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `frame-ancestors` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors).
Datatype: `string`

<note>
  The `frame-ancestors` directive can also be configured by using [`server.securityResponseHeaders.disableEmbedding`](#server-securityresponseheaders-disableembedding). In that case, that takes precedence and any values in `csp.frame_ancestors` are ignored.
</note>

  </definition>
  <definition term="csp.report_only.form_action">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `form-action` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/form-action) in reporting mode.
Datatype: `string`
  </definition>
  <definition term="csp.report_only.object_src">
    <stack-availability>Elastic Stack: Deprecated since 9.3</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `object-src` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/object-src) in reporting mode.
Datatype: `string`

<admonition title="Deprecation details">
  This setting is deprecated in favor of `csp.object_src`.
</admonition>

  </definition>
  <definition term="csp.report_uri">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `report-uri` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/report-uri).
Datatype: `string`
  </definition>
  <definition term="csp.report_to">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Add sources for the [Content Security Policy `report-to` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/report-to).
Datatype: `string`
  </definition>
  <definition term="csp.strict">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Blocks Kibana access to any browser that does not enforce even rudimentary CSP rules. In practice, this disables support for older, less safe browsers like Internet Explorer.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="csp.warnLegacyBrowsers">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Shows a warning message after loading Kibana to any browser that does not enforce even rudimentary CSP rules, though Kibana is still accessible. This configuration is effectively ignored when [`csp.strict`](#csp-strict) is enabled.
Datatype: `bool`
Default: `true`
  </definition>
</definitions>

## Elasticsearch connection settings
<definitions>
  <definition term="elasticsearch.customHeaders">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Header names and values to send to Elasticsearch. Any custom headers cannot be overwritten by client-side headers, regardless of the [`elasticsearch.requestHeadersWhitelist`](#elasticsearch-requestheaderswhitelist) configuration.
Datatype: `string`
Default: `{}`
  </definition>
  <definition term="elasticsearch.hosts">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The URLs of the Elasticsearch instances to use for all your queries. All nodes listed here must be on the same cluster.
To enable SSL/TLS for outbound connections to Elasticsearch, use the `https` protocol in this setting.
Datatype: `string`
Default: `[ "http://localhost:9200" ]`
  </definition>
  <definition term="elasticsearch.publicBaseUrl">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The URL through which Elasticsearch is publicly accessible, if any. This will be shown to users in Kibana when they need connection details for your Elasticsearch cluster.
Datatype: `string`
  </definition>
  <definition term="elasticsearch.pingTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of the [`elasticsearch.requestTimeout`](#elasticsearch-requesttimeout) setting.
Datatype: `int`
  </definition>
  <definition term="elasticsearch.requestHeadersWhitelist">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

List of Kibana client-side headers to send to Elasticsearch. To send **no** client-side headers, set this value to [] (an empty list). Removing the `authorization` header from being whitelisted means that you cannot use [basic authentication](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication#basic-authentication) in Kibana.
Datatype: `string`
Default: `[ 'authorization', 'es-client-authentication' ]`
  </definition>
  <definition term="elasticsearch.requestTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Time in milliseconds to wait for responses from the back end or Elasticsearch. This value must be a positive integer.
Datatype: `int`
Default: `30000`
  </definition>
  <definition term="elasticsearch.shardTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
Datatype: `int`
Default: `30000`
  </definition>
  <definition term="elasticsearch.compression">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Specifies whether Kibana should use compression for communications with Elasticsearch.
It is available in Elastic Cloud 8.3.0 and later versions.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="elasticsearch.sniffInterval">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Time in milliseconds between requests to check Elasticsearch for an updated list of nodes.
Datatype: `string`
Default: `false`
  </definition>
  <definition term="elasticsearch.sniffOnStart">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Attempt to find other Elasticsearch nodes on startup.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="elasticsearch.sniffOnConnectionFault">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Update the list of Elasticsearch nodes immediately following a connection fault.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="elasticsearch.maxSockets">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The maximum number of sockets that can be used for communications with Elasticsearch.
It is available in Elastic Cloud 8.2.0 and later versions.
Datatype: `int`
Default: `800`
  </definition>
  <definition term="elasticsearch.maxResponseSize">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Either `false` or a `byteSize` value. When set, responses from Elasticsearch with a size higher than the defined limit will be rejected. This is intended to be used as a circuit-breaker mechanism to avoid memory errors in case of unexpectedly high responses coming from Elasticsearch.
Datatype: `string`
Default: `false`
  </definition>
  <definition term="elasticsearch.maxIdleSockets">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The maximum number of idle sockets to keep open between Kibana and Elasticsearch. If more sockets become idle, they will be closed.
Datatype: `int`
Default: `256`
  </definition>
  <definition term="elasticsearch.idleSocketTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The timeout for idle sockets kept open between Kibana and Elasticsearch. If the socket is idle for longer than this timeout, it will be closed. If you have a transparent proxy between Kibana and Elasticsearch be sure to set this value lower than or equal to the proxy's timeout.
Datatype: `string`
Default: `60s`
  </definition>
  <definition term="elasticsearch.username">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

If your Elasticsearch is protected with basic authentication, this setting provides the username that the Kibana server uses to perform maintenance on the Kibana index at startup. Kibana users still need to authenticate with Elasticsearch, which is proxied through the Kibana server.
Datatype: `string`
  </definition>
  <definition term="elasticsearch.password">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

If your Elasticsearch is protected with basic authentication, this setting provides the password that the Kibana server uses to perform maintenance on the Kibana index at startup. Kibana users still need to authenticate with Elasticsearch, which is proxied through the Kibana server.
Datatype: `string`
  </definition>
  <definition term="elasticsearch.serviceAccountToken">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

If your Elasticsearch is protected with basic authentication, this token provides the credentials that the Kibana server uses to perform maintenance on the Kibana index at startup. This setting is an alternative to `elasticsearch.username` and `elasticsearch.password`.
Datatype: `string`
  </definition>
</definitions>

## Elasticsearch SSL settings
<definitions>
  <definition term="elasticsearch.ssl.alwaysPresentCertificate">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Controls Kibana behavior in regard to presenting a client certificate when requested by Elasticsearch. This setting applies to all outbound SSL/TLS connections to Elasticsearch, including requests that are proxied for end users.
Datatype: `bool`
Default: `false`

<warning>
  When Elasticsearch uses certificates to authenticate end users with a PKI realm and [`elasticsearch.ssl.alwaysPresentCertificate`](#elasticsearch-ssl-alwayspresentcertificate) is `true`, proxied requests may be executed as the identity that is tied to the Kibana server.
</warning>

  </definition>
  <definition term="elasticsearch.ssl.certificate">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to a PEM-encoded X.509 client certificate. This is used by Kibana to authenticate itself when making outbound SSL/TLS connections to Elasticsearch. For this setting to take effect, the `xpack.security.http.ssl.client_authentication` setting in Elasticsearch must be also be set to `"required"` or `"optional"` to request a client certificate from Kibana.
Datatype: `string`

<note>
  This setting cannot be used in conjunction with [`elasticsearch.ssl.keystore.path`](#elasticsearch-ssl-keystore-path).
</note>

  </definition>
  <definition term="elasticsearch.ssl.key">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to the corresponding private key for the PEM-encoded X.509 client certificate specified via [`elasticsearch.ssl.certificate`](#elasticsearch-ssl-cert-key). These are used by Kibana to authenticate itself when making outbound SSL/TLS connections to Elasticsearch. For this setting to take effect, the `xpack.security.http.ssl.client_authentication` setting in Elasticsearch must be also be set to `"required"` or `"optional"` to request a client certificate from Kibana.
Datatype: `string`

<note>
  This setting cannot be used in conjunction with [`elasticsearch.ssl.keystore.path`](#elasticsearch-ssl-keystore-path).
</note>

  </definition>
  <definition term="elasticsearch.ssl.certificateAuthorities">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates, which make up a trusted certificate chain for Elasticsearch. This chain is used by Kibana to establish trust when making outbound SSL/TLS connections to Elasticsearch.
In addition to this setting, trusted certificates may be specified via [`elasticsearch.ssl.keystore.path`](#elasticsearch-ssl-keystore-path) and/or [`elasticsearch.ssl.truststore.path`](#elasticsearch-ssl-truststore-path).
Datatype: `string`
  </definition>
  <definition term="elasticsearch.ssl.keyPassphrase">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The password that decrypts the private key that is specified via [`elasticsearch.ssl.key`](#elasticsearch-ssl-cert-key). This value is optional, as the key may not be encrypted.
Datatype: `string`
  </definition>
  <definition term="elasticsearch.ssl.keystore.path">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to a PKCS#12 keystore that contains an X.509 client certificate and it's corresponding private key. These are used by Kibana to authenticate itself when making outbound SSL/TLS connections to Elasticsearch. For this setting, you must also set the `xpack.security.http.ssl.client_authentication` setting in Elasticsearch to `"required"` or `"optional"` to request a client certificate from Kibana.
If the keystore contains any additional certificates, they are used as a trusted certificate chain for Elasticsearch. This chain is used by Kibana to establish trust when making outbound SSL/TLS connections to Elasticsearch. In addition to this setting, trusted certificates may be specified via [`elasticsearch.ssl.certificateAuthorities`](#elasticsearch-ssl-certificateauthorities) and/or [`elasticsearch.ssl.truststore.path`](#elasticsearch-ssl-truststore-path).
Datatype: `string`

<note>
  This setting cannot be used in conjunction with [`elasticsearch.ssl.certificate`](#elasticsearch-ssl-cert-key) or [`elasticsearch.ssl.key`](#elasticsearch-ssl-cert-key).
</note>

  </definition>
  <definition term="elasticsearch.ssl.keystore.password">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The password that decrypts the keystore specified via [`elasticsearch.ssl.keystore.path`](#elasticsearch-ssl-keystore-path). If the keystore has no password, leave this as blank. If the keystore has an empty password, set this to `""`.
Datatype: `string`
  </definition>
  <definition term="elasticsearch.ssl.truststore.path">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to a PKCS#12 trust store that contains one or more X.509 certificate authority (CA) certificates, which make up a trusted certificate chain for Elasticsearch. This chain is used by Kibana to establish trust when making outbound SSL/TLS connections to Elasticsearch.
In addition to this setting, trusted certificates may be specified via [`elasticsearch.ssl.certificateAuthorities`](#elasticsearch-ssl-certificateauthorities) and/or [`elasticsearch.ssl.keystore.path`](#elasticsearch-ssl-keystore-path).
Datatype: `string`
  </definition>
  <definition term="elasticsearch.ssl.truststore.password">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The password that decrypts the trust store specified via [`elasticsearch.ssl.truststore.path`](#elasticsearch-ssl-truststore-path). If the trust store has no password, leave this as blank. If the trust store has an empty password, set this to `""`.
Datatype: `string`
  </definition>
  <definition term="elasticsearch.ssl.verificationMode">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Controls the verification of the server certificate that Kibana receives when making an outbound SSL/TLS connection to Elasticsearch. Valid values are `"full"`, `"certificate"`, and `"none"`. Using `"full"` performs hostname verification, using `"certificate"` skips hostname verification, and using `"none"` skips verification entirely.
Datatype: `enum`
Default: `full`
Options:
- `full`
- `certificate`
- `none`
  </definition>
</definitions>

## Logging settings
<definitions>
  <definition term="logging.root">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The `root` logger is a [dedicated logger](https://www.elastic.co/docs/deploy-manage/monitor/logging-configuration/kibana-logging#dedicated-loggers) and is pre-configured. The `root` logger logs at `info` level by default. If any other logging configuration is specified, `root` *must* also be explicitly configured.
Datatype: `string`
  </definition>
  <definition term="logging.root.appenders">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

A list of logging appenders to forward the root level logger instance to. By default `root` is configured with the `default` appender that logs to stdout with a `pattern` layout. This is the configuration that all custom loggers will use unless they're re-configured explicitly. You can override the default behavior by configuring a different [appender](https://www.elastic.co/docs/deploy-manage/monitor/logging-configuration/kibana-logging#logging-appenders) to apply to `root`.
Datatype: `string`
  </definition>
  <definition term="logging.root.level">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Level at which a log record should be logged. Supported levels are: *all*, *fatal*, *error*, *warn*, *info*, *debug*, *trace*, *off*. Levels are ordered from *all* (highest) to *off* and a log record will be logged it its level is higher than or equal to the level of its logger, otherwise the log record is ignored. Use this value to [change the overall log level](https://www.elastic.co/docs/deploy-manage/monitor/logging-configuration/kibana-log-settings-examples#change-overall-log-level).
Datatype: `enum`
Default: `info`
Options:
- `all`
- `fatal`
- `error`
- `warn`
- `info`
- `debug`
- `trace`
- `off`

<tip>
  Set to `all` to log all events, including system usage information and all requests. Set to `off` to silence all logs. You can also use the logging [cli commands](https://www.elastic.co/docs/deploy-manage/monitor/logging-configuration/kib-advanced-logging#logging-cli-migration) to set log level to `verbose` or silence all logs.
</tip>


The following example shows a valid verbose `logging.root` configuration:
```text
logging:
  appenders:
    console_appender:
      type: console
      layout:
        type: pattern
        highlight: true
  root:
    appenders: [console_appender]
    level: all
```

  </definition>
  <definition term="logging.loggers[]">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Allows you to [customize a specific logger instance](https://www.elastic.co/docs/deploy-manage/monitor/logging-configuration/kibana-log-settings-examples#customize-specific-log-records).
Datatype: `string`
  </definition>
  <definition term="logging.appenders[]">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

[Appenders](https://www.elastic.co/docs/deploy-manage/monitor/logging-configuration/kibana-logging#logging-appenders) define how and where log messages are displayed (eg. **stdout** or console) and stored (eg. file on the disk).
Datatype: `string`
  </definition>
</definitions>

## Map settings
<definitions>
  <definition term="map.includeElasticMapsService">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Set to `false` to disable connections to Elastic Maps Service. When `includeElasticMapsService` is turned off, only tile layer configured by [`map.tilemap.url`](#tilemap-url) is available in [Maps](https://www.elastic.co/docs/explore-analyze/visualize/maps).
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="map.emsUrl">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Specifies the URL of a self hosted [Elastic Maps Server](https://www.elastic.co/docs/explore-analyze/visualize/maps/maps-connect-to-ems#elastic-maps-server)
Datatype: `string`
  </definition>
  <definition term="map.tilemap.options.attribution">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The map attribution string. Provide attributions in markdown and use `\|` to delimit attributions, for example: `"[attribution 1](https://www.attribution1)\|[attribution 2](https://www.attribution2)"`.
Datatype: `string`
Default: `"© [Elastic Maps Service](https://www.elastic.co/elastic-maps-service)"`
  </definition>
  <definition term="map.tilemap.options.maxZoom">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The maximum zoom level.
Datatype: `int`
Default: `10`
  </definition>
  <definition term="map.tilemap.options.minZoom">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The minimum zoom level.
Datatype: `int`
Default: `1`
  </definition>
  <definition term="map.tilemap.options.subdomains">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

An array of subdomains used by the tile service. Specify the position of the subdomain the URL with the token `{{s}}`.
Datatype: `string`
  </definition>
  <definition term="map.tilemap.url">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The URL to the service that Kibana uses as the default basemap in [maps](https://www.elastic.co/docs/explore-analyze/visualize/maps) and [vega maps](https://www.elastic.co/docs/explore-analyze/visualize/custom-visualizations-with-vega#vega-with-a-map). By default, Kibana sets a basemap from the [Elastic Maps Service](https://www.elastic.co/docs/explore-analyze/visualize/maps/maps-connect-to-ems), but users can point to their own Tile Map Service. For example: `"https://tiles.elastic.co/v2/default/{{z}}/{x}/{{y}}.png?elastic_tile_service_tos=agree&my_app_name=kibana"`
Datatype: `string`
  </definition>
</definitions>

## Migrations settings
<definitions>
  <definition term="migrations.batchSize">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Defines the number of documents migrated at a time. The higher the value, the faster the Saved Objects migration process performs at the cost of higher memory consumption. If upgrade migrations results in Kibana crashing with an out of memory exception or fails due to an Elasticsearch `circuit_breaking_exception`, use a smaller `batchSize` value to reduce the memory pressure.
Datatype: `int`
Default: `1000`
  </definition>
  <definition term="migrations.discardUnknownObjects">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Discard saved objects with unknown types during a migration. Must be set to the target version, for example: `8.4.0`. Default: undefined.
It is available in Elastic Cloud 8.4.0 and later versions.
Datatype: `string`
  </definition>
  <definition term="migrations.discardCorruptObjects">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Discard corrupt saved objects, as well as those that cause transform errors during a migration. Must be set to the target version, for example: `8.4.0`. Default: undefined.
It is available in Elastic Cloud 8.4.0 and later versions.
Datatype: `string`
  </definition>
  <definition term="migrations.maxBatchSizeBytes">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Defines the maximum payload size for indexing batches of upgraded saved objects to avoid migrations failing due to a 413 Request Entity Too Large response from Elasticsearch. This value should be lower than or equal to your Elasticsearch cluster's `http.max_content_length` configuration option.
Datatype: `string`
Default: `100mb`
  </definition>
  <definition term="migrations.retryAttempts">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The number of times migrations retry temporary failures, such as a network timeout, 503 status code, or `snapshot_in_progress_exception`. When upgrade migrations frequently fail after exhausting all retry attempts with a message such as `Unable to complete the [...] step after 15 attempts, terminating.`, increase the setting value.
Datatype: `int`
Default: `15`
  </definition>
  <definition term="migrations.useCumulativeLogger">
    <stack-availability>Elastic Stack: Generally available since 9.2</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Skip logging migration progress unless there are any errors. Set to `false` when troubleshooting migration issues and not automatically shown.
Datatype: `bool`
Default: `true`
  </definition>
</definitions>

## Saved Objects settings
<definitions>
  <definition term="savedObjects.maxImportExportSize">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The maximum count of saved objects that can be imported or exported. This setting exists to prevent the Kibana server from running out of memory when handling large numbers of saved objects. It is recommended to only raise this setting if you are confident your server can hold this many objects in memory.
Datatype: `int`
Default: `10000`
  </definition>
  <definition term="savedObjects.maxImportPayloadBytes">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The maximum byte size of a saved objects import that the Kibana server will accept. This setting exists to prevent the Kibana server from running out of memory when handling a large import payload. Note that this setting overrides the more general [`server.maxPayload`](#server-maxpayload) for saved object imports only.
Datatype: `int`
Default: `26214400`
  </definition>
</definitions>

## Search and autocomplete settings
<definitions>
  <definition term="data.autocomplete.valueSuggestions.terminateAfter">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Specifies the max number of documents loaded by each shard to generate autocomplete suggestions. Allowed values are between 1 and 10000000.
Datatype: `int`
Default: `100000`
  </definition>
  <definition term="data.autocomplete.valueSuggestions.timeout">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Specifies the time in milliseconds to wait for autocomplete suggestions from Elasticsearch. Allowed values are between 1 and 1200000.
Datatype: `int`
Default: `1000`
  </definition>
  <definition term="unifiedSearch.autocomplete.valueSuggestions.timeout">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Time in milliseconds to wait for autocomplete suggestions from Elasticsearch. This value must be a whole number greater than zero.
Datatype: `int`
Default: `1000`
  </definition>
  <definition term="unifiedSearch.autocomplete.valueSuggestions.terminateAfter">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Maximum number of documents loaded by each shard to generate autocomplete suggestions. This value must be a whole number greater than zero.
Datatype: `int`
Default: `100000`

<note>
  To reload the logging settings, send a SIGHUP signal to Kibana. For more logging configuration options, see the [Configure Logging in Kibana](https://www.elastic.co/docs/deploy-manage/monitor/logging-configuration/kibana-logging) guide.
</note>

  </definition>
</definitions>

## Server settings
<definitions>
  <definition term="server.basePath">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Enables you to specify a path to mount Kibana at if you are running behind a proxy. Use the [`server.rewriteBasePath`](#server-rewritebasepath) setting to tell Kibana if it should remove the basePath from requests it receives, and to prevent a deprecation warning at startup. This setting cannot end in a slash (`/`).
Datatype: `string`
  </definition>
  <definition term="server.publicBaseUrl">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The publicly available URL that end-users access Kibana at. Must include the protocol, hostname, port (if different than the defaults for `http` and `https`, 80 and 443 respectively), and the [`server.basePath`](#server-basePath) (when that setting is configured explicitly). This setting cannot end in a slash (`/`).
Datatype: `string`
  </definition>
  <definition term="server.host">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

This setting specifies the host of the back end server. To allow remote users to connect, set the value to the IP address or DNS name of the Kibana server. Use `0.0.0.0` to make Kibana listen on all IPs (public and private).
Datatype: `string`
Default: `"localhost"`
  </definition>
  <definition term="server.keepaliveTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The number of milliseconds to wait for additional data before restarting the [`server.socketTimeout`](#server-sockettimeout) counter.
Datatype: `int`
Default: `120000`
  </definition>
  <definition term="server.maxPayload">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The maximum payload size in bytes for incoming server requests.
Datatype: `int`
Default: `1048576`
  </definition>
  <definition term="server.name">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

A human-readable display name that identifies this Kibana instance.
Datatype: `string`
Default: `"your-hostname"`
  </definition>
  <definition term="server.port">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Kibana is served by a back end server. This setting specifies the port to use.
Datatype: `int`
Default: `5601`
  </definition>
  <definition term="server.protocol">
    <stack-availability>Elastic Stack: Preview</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The HTTP protocol to use, either `http1` or `http2`. Set to `http1` to opt out of `HTTP/2` support when TLS is enabled. Use of `http1` may impact browser loading performance especially for dashboards with many panels. Default is `http2` if TLS is enabled, otherwise `http1`.
Datatype: `enum`
Options:
- `http1`
- `http2`

<note>
  By default, enabling `http2` requires a valid `h2c` configuration, meaning that TLS must be enabled via [`server.ssl.enabled`](#server-ssl-enabled) and [`server.ssl.supportedprotocols`](#server-ssl-supportedProtocols), if specified, must contain at least `TLSv1.2` or `TLSv1.3`. Strict validation of the `h2c` setup can be disabled by adding `server.http2.allowUnsecure: true` to the configuration.
</note>

  </definition>
  <definition term="server.shutdownTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Sets the grace period for Kibana to attempt to resolve any ongoing HTTP requests after receiving a `SIGTERM`/`SIGINT` signal, and before shutting down. Any new HTTP requests received during this period are rejected, because the incoming socket is closed without further processing.
Datatype: `string`
Default: `30s`
  </definition>
  <definition term="server.socketTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The number of milliseconds to wait before closing an inactive socket.
Datatype: `int`
Default: `120000`
  </definition>
  <definition term="server.payloadTimeout">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Sets the maximum time allowed for the client to transmit the request payload (body) before giving up and responding with a Request Timeout (408) error response.
Datatype: `int`
Default: `20000`
  </definition>
  <definition term="server.customResponseHeaders">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Header names and values to send on all responses to the client from the Kibana server.
Datatype: `string`
Default: `{}`
  </definition>
  <definition term="server.requestId.allowFromAnyIp">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Sets whether or not the `X-Opaque-Id` header should be trusted from any IP address for identifying requests in logs and forwarded to Elasticsearch.
Datatype: `bool`
  </definition>
  <definition term="server.requestId.ipAllowlist">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

A list of IPv4 and IPv6 address which the `X-Opaque-Id` header should be trusted from. Normally this would be set to the IP addresses of the load balancers or reverse-proxy that end users use to access Kibana. If any are set, [`server.requestId.allowFromAnyIp`](#server-requestid-allowfromanyip) must also be set to `false.`
Datatype: `string`
  </definition>
  <definition term="server.rewriteBasePath">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Specifies whether Kibana should rewrite requests that are prefixed with [`server.basePath`](#server-basepath) or require that they are rewritten by your reverse proxy.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="server.uuid">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The unique identifier for this Kibana instance. It must be a valid UUIDv4. It gets automatically generated on the first startup if not specified and persisted in the `data` path.
Datatype: `string`
  </definition>
</definitions>

## Server compression settings
<definitions>
  <definition term="server.compression.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set to `false` to disable HTTP compression for all responses.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="server.compression.referrerWhitelist">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Specifies an array of trusted hostnames, such as the Kibana host, or a reverse proxy sitting in front of it. This determines whether HTTP compression may be used for responses, based on the request `Referer` header. This setting may not be used when [`server.compression.enabled`](#server-compression) is set to `false`.
Datatype: `string`
  </definition>
  <definition term="server.compression.brotli.enabled">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Set to `true` to enable brotli (br) compression format. Browsers not supporting brotli compression will fallback to using gzip instead. This setting may not be used when [`server.compression.enabled`](#server-compression) is set to `false`.
It is available in Elastic Cloud 8.6.0 and later versions.
Datatype: `bool`
Default: `false`
  </definition>
</definitions>

## Server CORS settings
<definitions>
  <definition term="server.cors.enabled">
    <stack-availability>Elastic Stack: Preview</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set to `true` to allow cross-origin API calls.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="server.cors.allowCredentials">
    <stack-availability>Elastic Stack: Preview</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set to `true` to allow browser code to access response body whenever request performed with user credentials.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="server.cors.allowOrigin">
    <stack-availability>Elastic Stack: Preview</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

List of origins permitted to access resources. You must specify explicit hostnames and not use `server.cors.allowOrigin: ["*"]` when `server.cors.allowCredentials: true`.
Datatype: `string`
Default: `["*"]`
  </definition>
</definitions>

## Server rate limiter settings
<definitions>
  <definition term="server.rateLimiter.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Enables rate-limiting of requests to the Kibana server based on Node.js' Event Loop Utilization. If the average event loop utilization for the specified term exceeds the configured threshold, the server will respond with a `429 Too Many Requests` status code.
This functionality should be used carefully as it may impact the server's availability. The configuration options vary per environment, so it is recommended to enable this option in a testing environment first, adjust the rate-limiter configuration, and then roll it out to production.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="server.rateLimiter.elu">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The Event Loop Utilization (ELU) threshold for rate-limiting requests to the Kibana server. The ELU is a value between 0 and 1, representing the average event loop utilization over the specified term. If the average ELU exceeds this threshold, the server will respond with a `429 Too Many Requests` status code.
In a multi-instance environment with autoscaling, this value is usually between 0.6 and 0.8 to give the autoscaler enough time to react. This value can be higher in a single-instance environment but should not exceed 1.0. In general, the lower the value, the more aggressive the rate limiting. And the highest possible option should be used to prevent the Kibana server from being terminated.
Datatype: `float`
  </definition>
  <definition term="server.rateLimiter.term">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

This value is one of `short`, `medium`, or `long`, representing the term over which the average event loop utilization is calculated. It uses exponential moving averages (EMA) to smooth out the utilization values. Each term corresponds to `15s`, `30s`, and `60s`, respectively.
The term value also changes the way the rate limiter sees the trend in the load:
- `short`: `elu.short > server.rateLimiter.term`;
- `medium`: `elu.short > server.rateLimiter.elu AND elu.medium > server.rateLimiter.elu`;
- `long`: `elu.short > server.rateLimiter.elu AND elu.medium > server.rateLimiter.elu AND elu.long > server.rateLimiter.elu`.

This behavior prevents requests from being throttled if the load starts decreasing. In general, the shorter the term, the more aggressive the rate limiting. In the multi-instance environment, the `medium` term makes the most sense as it gives the Kibana server enough time to spin up a new instance and prevents the existing instances from being terminated.
Datatype: `enum`
Options:
- `short`
- `medium`
- `long`
  </definition>
</definitions>

## Server security response headers
<definitions>
  <definition term="server.securityResponseHeaders.strictTransportSecurity">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls whether the [`Strict-Transport-Security`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) header is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are any text value or `null`. To disable, set to `null`.
Datatype: `string`
Default: `null`
  </definition>
  <definition term="server.securityResponseHeaders.xContentTypeOptions">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls whether the [`X-Content-Type-Options`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options) header is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are `nosniff` or `null`. To disable, set to `null`.
Datatype: `string`
Default: `"nosniff"`
  </definition>
  <definition term="server.securityResponseHeaders.referrerPolicy">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls whether the [`Referrer-Policy`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy) header is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are `no-referrer`, `no-referrer-when-downgrade`, `origin`, `origin-when-cross-origin`, `same-origin`, `strict-origin`, `strict-origin-when-cross-origin`, `unsafe-url`, or `null`. To disable, set to `null`.
Datatype: `string`
Default: `"strict-origin-when-cross-origin"`
  </definition>
  <definition term="server.securityResponseHeaders.permissionsPolicy">
    <stack-availability>Elastic Stack: Preview</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls whether the [`Permissions-Policy`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) header is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are any text value or `null`. Refer to the [`Permissions-Policy` documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) for defined directives, values, and text format. To disable, set to `null`.
Datatype: `string`
Default: `camera=(), display-capture=(), fullscreen=(self), geolocation=(), microphone=(), web-share=()`
  </definition>
  <definition term="server.securityResponseHeaders.permissionsPolicyReportOnly">
    <stack-availability>Elastic Stack: Preview</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls whether the [`Permissions-Policy-Report-Only`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) header is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are any text value or `null`. Refer to the [`Permissions-Policy` documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) for defined directives, values, and text format.
Datatype: `string`
  </definition>
  <definition term="server.securityResponseHeaders.disableEmbedding">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls whether the [`Content-Security-Policy`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) and [`X-Frame-Options`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options) headers are configured to disable embedding Kibana in other webpages using iframes. When set to `true`, secure headers are used to disable embedding, which adds the `frame-ancestors: 'self'` directive to the `Content-Security-Policy` response header and adds the `X-Frame-Options: SAMEORIGIN` response header.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="server.securityResponseHeaders.crossOriginOpenerPolicy">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls whether the [`Cross-Origin-Opener-Policy`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy) header is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are `unsafe-none`, `same-origin-allow-popups`, `same-origin`, or `null`. To disable, set to `null`.
It is available in Elastic Cloud 8.7.0 and later versions.
Datatype: `enum`
Default: `"same-origin"`
Options:
- `unsafe-none`
- `same-origin-allow-popups`
- `same-origin`
- `null`
  </definition>
</definitions>

## Server SSL settings
<definitions>
  <definition term="server.ssl.certificate">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to a PEM-encoded X.509 server certificate. This is used by Kibana to establish trust when receiving inbound SSL/TLS connections from users.
Datatype: `string`

<note>
  This setting cannot be used in conjunction with [`server.ssl.keystore.path`](#server-ssl-keystore-path).
</note>

  </definition>
  <definition term="server.ssl.key">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to the corresponding private key for the PEM-encoded X.509 server certificate specified via [`server.ssl.certificate`](#server-ssl-cert-key). This is used by Kibana to establish trust when receiving inbound SSL/TLS connections from users.
Datatype: `string`

<note>
  This setting cannot be used in conjunction with [`server.ssl.keystore.path`](#server-ssl-keystore-path).
</note>

  </definition>
  <definition term="server.ssl.certificateAuthorities">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates which make up a trusted certificate chain for Kibana. This chain is used by Kibana to establish trust when receiving inbound SSL/TLS connections from end users. If PKI authentication is enabled, this chain is also used by Kibana to verify client certificates from end users.
In addition to this setting, trusted certificates may be specified via [`server.ssl.keystore.path`](#server-ssl-keystore-path) and/or [`server.ssl.truststore.path`](#server-ssl-truststore-path).
Datatype: `string`
  </definition>
  <definition term="server.ssl.cipherSuites">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Details on the format, and the valid options, are available via the [OpenSSL cipher list format documentation](https://www.openssl.org/docs/man1.1.1/man1/ciphers.md#CIPHER-LIST-FORMAT).
Datatype: `string`
Default: `TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256, ECDHE-ECDSA-AES128-GCM-SHA256, ECDHE-RSA-AES256-GCM-SHA384, ECDHE-ECDSA-AES256-GCM-SHA384, DHE-RSA-AES128-GCM-SHA256, ECDHE-RSA-AES128-SHA256, DHE-RSA-AES128-SHA256, ECDHE-RSA-AES256-SHA384, DHE-RSA-AES256-SHA384, ECDHE-RSA-AES256-SHA256, DHE-RSA-AES256-SHA256, HIGH,!aNULL, !eNULL, !EXPORT, !DES, !RC4, !MD5, !PSK, !SRP, !CAMELLIA`
  </definition>
  <definition term="server.ssl.clientAuthentication">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Controls the behavior in Kibana for requesting a certificate from client connections. Valid values are `"required"`, `"optional"`, and `"none"`. Using `"required"` will refuse to establish the connection unless a client presents a certificate, using `"optional"` will allow a client to present a certificate if it has one, and using `"none"` will prevent a client from presenting a certificate.
Datatype: `enum`
Default: `"none"`
Options:
- `required`
- `optional`
- `none`
  </definition>
  <definition term="server.ssl.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Enables SSL/TLS for inbound connections to Kibana. When set to `true`, a certificate and its corresponding private key must be provided. These can be specified via [`server.ssl.keystore.path`](#server-ssl-keystore-path) or the combination of [`server.ssl.certificate`](#server-ssl-cert-key) and [`server.ssl.key`](#server-ssl-cert-key).
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="server.ssl.keyPassphrase">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The password that decrypts the private key that is specified via [`server.ssl.key`](#server-ssl-cert-key). This value is optional, as the key may not be encrypted.
Datatype: `string`
  </definition>
  <definition term="server.ssl.keystore.path">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to a PKCS#12 keystore that contains an X.509 server certificate and its corresponding private key. If the keystore contains any additional certificates, those will be used as a trusted certificate chain for Kibana. All of these are used by Kibana to establish trust when receiving inbound SSL/TLS connections from end users. The certificate chain is also used by Kibana to verify client certificates from end users when PKI authentication is enabled.
In addition to this setting, trusted certificates may be specified via [`server.ssl.certificateAuthorities`](#server-ssl-certificateauthorities) and/or [`server.ssl.truststore.path`](#server-ssl-truststore-path).
Datatype: `string`

<note>
  This setting cannot be used in conjunction with [`server.ssl.certificate`](#server-ssl-cert-key) or [`server.ssl.key`](#server-ssl-cert-key).
</note>

  </definition>
  <definition term="server.ssl.keystore.password">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The password that will be used to decrypt the keystore specified via [`server.ssl.keystore.path`](#server-ssl-keystore-path). If the keystore has no password, leave this unset. If the keystore has an empty password, set this to `""`.
Datatype: `string`
  </definition>
  <definition term="server.ssl.truststore.path">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Path to a PKCS#12 trust store that contains one or more X.509 certificate authority (CA) certificates which make up a trusted certificate chain for Kibana. This chain is used by Kibana to establish trust when receiving inbound SSL/TLS connections from end users. If PKI authentication is enabled, this chain is also used by Kibana to verify client certificates from end users.
In addition to this setting, trusted certificates may be specified via [`server.ssl.certificateAuthorities`](#server-ssl-certificateauthorities) and/or [`server.ssl.keystore.path`](#server-ssl-keystore-path).
Datatype: `string`
  </definition>
  <definition term="server.ssl.truststore.password">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The password that will be used to decrypt the trust store specified via [`server.ssl.truststore.path`](#server-ssl-truststore-path). If the trust store has no password, leave this unset. If the trust store has an empty password, set this to `""`.
Datatype: `string`
  </definition>
  <definition term="server.ssl.redirectHttpFromPort">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Kibana binds to this port and redirects all http requests to https over the port configured as [`server.port`](#server-port).
Datatype: `int`
  </definition>
  <definition term="server.ssl.supportedProtocols">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

An array of supported protocols with versions. Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`, `TLSv1.3`. Enabling `TLSv1.1` would require both setting the `--tls-min-1.1` option in the `node.options` configuration and adding `TLSv1.1` to `server.ssl.supportedProtocols`. `HTTP/2` requires the use of minimum `TLSv1.2` for secure connections.
Datatype: `string`
Default: `TLSv1.2, TLSv1.3`
  </definition>
</definitions>

## Server XSRF settings
<definitions>
  <definition term="server.xsrf.allowlist">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

It is not recommended to disable protections for arbitrary API endpoints. Instead, supply the `kbn-xsrf` header. The [`server.xsrf.allowlist`](#settings-xsrf-allowlist) setting requires the following format:
```text
*Default: [ ]* An array of API endpoints which should be exempt from Cross-Site Request Forgery ("XSRF") protections.
```

It is available in Elastic Cloud 8.0.0 and later versions.
Datatype: `string`
Default: `[]`
  </definition>
  <definition term="server.xsrf.disableProtection">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Setting this to `true` will completely disable Cross-site request forgery protection in Kibana. This is not recommended.
Datatype: `bool`
Default: `false`
  </definition>
</definitions>

## Telemetry settings
<definitions>
  <definition term="telemetry.allowChangingOptInStatus">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

When `false`, users cannot change the opt-in status through [Advanced Settings](https://www.elastic.co/docs/reference/kibana/advanced-settings), and Kibana only looks at the value of [`telemetry.optIn`](#settings-telemetry-optin) to determine whether to send telemetry data or not.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="telemetry.optIn">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set to `false` to stop sending any telemetry data to Elastic. Reporting your cluster statistics helps us improve your user experience. When `false`, the telemetry data is never sent to Elastic.
This setting can be changed at any time in [Advanced Settings](https://www.elastic.co/docs/reference/kibana/advanced-settings). To prevent users from changing it, set [`telemetry.allowChangingOptInStatus`](#telemetry-allowchangingoptinstatus) to `false`.
Datatype: `bool`
Default: `true`
  </definition>
</definitions>

## UI and visualization settings
<definitions>
  <definition term="uiSettings.globalOverrides.hideAnnouncements">
    <stack-availability>Elastic Stack: Planned</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Set to `true` to stop showing messages and tours that highlight new features.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="uiSettings.globalOverrides.hideFeedback">
    <stack-availability>Elastic Stack: Planned</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Set to `true` to stop showing elements requesting user feedback.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="vis_type_table.legacyVisEnabled">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Starting from version 7.11, a new datatable visualization is used. Set to `true` to enable the legacy version. In version 8.0 and later, the old implementation is removed and this setting is no longer supported.
Datatype: `bool`
  </definition>
  <definition term="vis_type_vega.enable">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

For 7.7 version and later, set to `false` to disable Vega vizualizations.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="vega.enableExternalUrls">
    <stack-availability>Elastic Stack: Deprecated since 8.0</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Set to `true` to allow Vega vizualizations to use data from sources other than the linked Elasticsearch cluster. In version 8.0 and later, the `vega.enableExternalUrls` is not supported. Use `vis_type_vega.enableExternalUrls` instead.
Datatype: `bool`

<admonition title="Deprecation details">
  In version 8.0 and later, this setting is not supported. Use `vis_type_vega.enableExternalUrls` instead.
</admonition>

  </definition>
  <definition term="vis_type_vega.enableExternalUrls">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Set this value to true to allow Vega to use any URL to access external data sources and images. When false, Vega can only get data from Elasticsearch.
Datatype: `bool`
Default: `false`
  </definition>
</definitions>

## Feature and plugin settings
<definitions>
  <definition term="xpack.ccr.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the Cross-Cluster Replication UI.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="xpack.discoverEnhanced.actions.exploreDataInContextMenu.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Enables the **Explore underlying data** option that allows you to open **Discover** from a dashboard panel and view the panel data.
When you create visualizations using the **Lens** drag-and-drop editor, you can use the toolbar to open and explore your data in **Discover**. For more information, check out [Explore the data in Discover](https://www.elastic.co/docs/explore-analyze/visualize/lens#explore-lens-data-in-discover).
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="xpack.discoverEnhanced.actions.exploreDataInChart.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Enables you to view the underlying documents in a data series from a dashboard panel.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="xpack.ilm.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the Index Lifecycle Policies UI.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="xpack.index_management.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the Index Management UI.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="xpack.license_management.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the License Management UI.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="xpack.remote_clusters.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the Remote Clusters UI.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="xpack.rollup.ui.enabled">
    <stack-availability>Elastic Stack: Deprecated since 8.11</stack-availability>
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the Rollup Jobs UI.
Datatype: `bool`
Default: `true`

<admonition title="Deprecation details">
  Rollups are deprecated and will be removed in a future version. Use [downsampling](https://www.elastic.co/docs/manage-data/data-store/data-streams/downsampling-time-series-data-stream) instead.
</admonition>

  </definition>
  <definition term="xpack.securitySolution.maxUploadResponseActionFileBytes">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Allow to configure the max file upload size for use with the Upload File Response action available with the Defend Integration. To learn more, check [Endpoint Response actions](https://www.elastic.co/docs/solutions/security/endpoint-response-actions).
It is available in Elastic Cloud 8.9.0 and later versions.
Datatype: `string`
  </definition>
  <definition term="xpack.securitySolution.disableEndpointRuleAutoInstall">
    <stack-availability>Elastic Stack: Generally available since 9.2</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Set to `true` to disable the automatic installation of Elastic Defend SIEM rules when a new Endpoint integration policy is created. Introduced with v9.2.4.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="xpack.securitySolution.maxEndpointScriptFileSize">
    <stack-availability>Elastic Stack: Planned</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The maximum file size in bytes for scripts uploaded to the Elastic Defend script library. Default is `26214400` (25MB).
Datatype: `bool`
Default: `26214400`
  </definition>
  <definition term="xpack.snapshot_restore.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the Snapshot and Restore UI.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="xpack.upgrade_assistant.ui.enabled">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

Set this value to false to disable the Upgrade Assistant UI.
Datatype: `bool`
Default: `true`
  </definition>
</definitions>