General settings in Kibana
ECH Self-Managed
If a setting is applicable to Elastic Cloud Hosted environments, its name is followed by this icon:
console.ui.enabled- Toggling this causes the server to regenerate assets on the next startup, which may cause a delay before pages start being served. Set to
falseto disable Console. Default:true csp.script_src- Add sources for the Content Security Policy
script-srcdirective. csp.disableUnsafeEval-
Deprecated in 8.7.0. Use
csp.script_src: ['unsafe-eval']instead if you wish to enableunsafe-eval. This config option will have no effect in a future version. Set this tofalseto add theunsafe-evalsource expression to thescript-srcdirective. Default:trueWhen
csp.disableUnsafeEvalis set totrue, 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 tofalseand open an issue in the Kibana GitHub repository. csp.worker_src- Add sources for the Content Security Policy
worker-srcdirective. csp.style_src- Add sources for the Content Security Policy
style-srcdirective. csp.connect_src- Add sources for the Content Security Policy
connect-srcdirective. csp.default_src- Add sources for the Content Security Policy
default-srcdirective. csp.font_src- Add sources for the Content Security Policy
font-srcdirective. csp.frame_src- Add sources for the Content Security Policy
frame-srcdirective. csp.img_src- Add sources for the Content Security Policy
img-srcdirective. csp.frame_ancestors-
Add sources for the Content Security Policy
frame-ancestorsdirective.NoteThe
frame-ancestorsdirective can also be configured by usingserver.securityResponseHeaders.disableEmbedding. In that case, that takes precedence and any values incsp.frame_ancestorsare ignored. csp.report_only.form_action- Add sources for the Content Security Policy
form-actiondirective in reporting mode. csp.report_only.object_src- Add sources for the Content Security Policy
object-srcdirective in reporting mode. csp.report_uri- Add sources for the Content Security Policy
report-uridirective. csp.report_to:- Add sources for the Content Security Policy
report-todirective. -
csp.strict - 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.
csp.warnLegacyBrowsers- 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.strictis enabled. Default:true data.autocomplete.valueSuggestions.terminateAfter-
Specifies the max number of documents loaded by each shard to generate autocomplete suggestions. The default is 100000. Allowed values are between 1 and 10000000.
data.autocomplete.valueSuggestions.timeout-
Specifies the time in milliseconds to wait for autocomplete suggestions from Elasticsearch. The default is 1000. Allowed values are between 1 and 1200000.
-
elasticsearch.maxSockets - The maximum number of sockets that can be used for communications with Elasticsearch. Default:
InfinityIt is available in Elastic Cloud 8.2.0 and later versions. -
elasticsearch.maxResponseSize - Either
falseor abyteSizevalue. 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. Default:false -
elasticsearch.maxIdleSockets - The maximum number of idle sockets to keep open between Kibana and Elasticsearch. If more sockets become idle, they will be closed. Default:
256 -
elasticsearch.idleSocketTimeout - 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. Default:
60s elasticsearch.customHeaders- Header names and values to send to Elasticsearch. Any custom headers cannot be overwritten by client-side headers, regardless of the
elasticsearch.requestHeadersWhitelistconfiguration. Default:{} -
elasticsearch.hosts: -
The URLs of the Elasticsearch instances to use for all your queries. All nodes listed here must be on the same cluster. Default:
[ "http://localhost:9200" ]To enable SSL/TLS for outbound connections to Elasticsearch, use the
httpsprotocol in this setting. -
elasticsearch.publicBaseUrl: - 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.
-
elasticsearch.pingTimeout - Time in milliseconds to wait for Elasticsearch to respond to pings. Default: the value of the
elasticsearch.requestTimeoutsetting -
elasticsearch.requestHeadersWhitelist - 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
authorizationheader from being whitelisted means that you cannot use basic authentication in Kibana. Default:[ 'authorization', 'es-client-authentication' ] -
elasticsearch.requestTimeout - Time in milliseconds to wait for responses from the back end or Elasticsearch. This value must be a positive integer. Default:
30000 elasticsearch.shardTimeout- Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable. Default:
30000 elasticsearch.compression- Specifies whether Kibana should use compression for communications with Elasticsearch.
Default:
falseIt is available in Elastic Cloud 8.3.0 and later versions. elasticsearch.sniffInterval- Time in milliseconds between requests to check Elasticsearch for an updated list of nodes. Default:
false elasticsearch.sniffOnStart- Attempt to find other Elasticsearch nodes on startup. Default:
false elasticsearch.sniffOnConnectionFault- Update the list of Elasticsearch nodes immediately following a connection fault. Default:
false -
elasticsearch.ssl.alwaysPresentCertificate -
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. Default:
falseWarningWhen Elasticsearch uses certificates to authenticate end users with a PKI realm and
elasticsearch.ssl.alwaysPresentCertificateistrue, proxied requests may be executed as the identity that is tied to the Kibana server. -
elasticsearch.ssl.certificateandelasticsearch.ssl.key -
Paths to a PEM-encoded X.509 client certificate and its corresponding private 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_authenticationsetting in Elasticsearch must be also be set to"required"or"optional"to request a client certificate from Kibana.NoteThese settings cannot be used in conjunction with
elasticsearch.ssl.keystore.path. -
elasticsearch.ssl.certificateAuthorities -
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.pathand/orelasticsearch.ssl.truststore.path. elasticsearch.ssl.keyPassphrase- The password that decrypts the private key that is specified via
elasticsearch.ssl.key. This value is optional, as the key may not be encrypted. -
elasticsearch.ssl.keystore.path -
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_authenticationsetting 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.certificateAuthoritiesand/orelasticsearch.ssl.truststore.path.NoteThis setting cannot be used in conjunction with
elasticsearch.ssl.certificateorelasticsearch.ssl.key. elasticsearch.ssl.keystore.password- The password that decrypts the keystore specified via
elasticsearch.ssl.keystore.path. If the keystore has no password, leave this as blank. If the keystore has an empty password, set this to"". -
elasticsearch.ssl.truststore.path -
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.certificateAuthoritiesand/orelasticsearch.ssl.keystore.path. elasticsearch.ssl.truststore.password- The password that decrypts the trust store specified via
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"". -
elasticsearch.ssl.verificationMode - 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. Default:"full" -
elasticsearch.usernameandelasticsearch.password - 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. Kibana users still need to authenticate with Elasticsearch, which is proxied through the Kibana server.
-
elasticsearch.serviceAccountToken - 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.usernameandelasticsearch.password. execution_context.enabled-
Propagate request-specific metadata to Elasticsearch server by way of the
x-opaque-idheader. It is available in Elastic Cloud 8.1.0 and later versions. -
logging.root - The
rootlogger has is a dedicated logger and is pre-configured. Therootlogger logs atinfolevel by default. If any other logging configuration is specified,rootmust also be explicitly configured. -
logging.root.appenders - A list of logging appenders to forward the root level logger instance to. By default
rootis configured with thedefaultappender that logs to stdout with apatternlayout. 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 to apply toroot. -
logging.root.level -
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. Default:
info.TipSet to
allto log all events, including system usage information and all requests. Set tooffto silence all logs. You can also use the logging cli commands to set log level toverboseor silence all logs.The following example shows a valid verbose
logging.rootconfiguration:logging: appenders: console_appender: type: console layout: type: pattern highlight: true root: appenders: [console_appender] level: all -
logging.loggers[] - Allows you to customize a specific logger instance.
logging.appenders[]- Appenders define how and where log messages are displayed (eg. stdout or console) and stored (eg. file on the disk).
map.includeElasticMapsService- Set to
falseto disable connections to Elastic Maps Service. WhenincludeElasticMapsServiceis turned off, only tile layer configured bymap.tilemap.urlis available in Maps. Default:true map.emsUrl- Specifies the URL of a self hosted Elastic Maps Server
-
map.tilemap.options.attribution - 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)". Default:"© [Elastic Maps Service](https://www.elastic.co/elastic-maps-service)" -
map.tilemap.options.maxZoom - The maximum zoom level. Default:
10 -
map.tilemap.options.minZoom - The minimum zoom level. Default:
1 -
map.tilemap.options.subdomains - An array of subdomains used by the tile service. Specify the position of the subdomain the URL with the token
{{s}}. -
map.tilemap.url - The URL to the service that Kibana uses as the default basemap in maps and vega maps. By default, Kibana sets a basemap from the Elastic Maps Service, 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" migrations.batchSize- 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 smallerbatchSizevalue to reduce the memory pressure. Default:1000 migrations.discardUnknownObjects-
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. migrations.discardCorruptObjects-
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. migrations.maxBatchSizeBytes- 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_lengthconfiguration option. Default:100mb migrations.retryAttempts- 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 asUnable to complete the [...] step after 15 attempts, terminating., increase the setting value. Default:15 migrations.useCumulativeLoggerStack- Skip logging migration progress unless there are any errors. Set to
falsewhen troubleshooting migration issues and not automatically shown. Default:true newsfeed.enabled- Controls whether to enable the newsfeed system for the Kibana UI notification center. Set to
falseto disable the newsfeed system. Default:true node.roles- Indicates which roles to configure the Kibana process with, which will effectively run Kibana in different modes. Valid options are
background_tasksandui, or*to select all roles. Default:*. This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. notifications.connectors.default.email- 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 in the system viakibana.yml, and the notifications plugin must be configured to point to the ID of that connector. ops.interval- Set the interval in milliseconds to sample system and process performance metrics. The minimum value is 100. Default:
5000 -
ops.cGroupOverrides.cpuPath - Override for cgroup cpu path when mounted in a manner that is inconsistent with
/proc/self/cgroup. -
ops.cGroupOverrides.cpuAcctPath - Override for cgroup cpuacct path when mounted in a manner that is inconsistent with
/proc/self/cgroup. -
path.data - The path where Kibana stores persistent data not saved in Elasticsearch. Default:
data permissionsPolicy.report_to:- Add sources for the Permissions Policy
report-todirective. pid.file- Specifies the path where Kibana creates the process ID file.
-
savedObjects.maxImportExportSize - 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. Default:
10000 -
savedObjects.maxImportPayloadBytes - 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.maxPayloadfor saved object imports only. Default:26214400 -
server.basePath - Enables you to specify a path to mount Kibana at if you are running behind a proxy. Use the
server.rewriteBasePathsetting 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 (/). server.defaultRoute-
Specifies the default route when opening Kibana. You can use this setting to modify the landing page when opening Kibana.
-
server.publicBaseUrl - The publicly available URL that end-users access Kibana at. Must include the protocol, hostname, port (if different than the defaults for
httpandhttps, 80 and 443 respectively), and theserver.basePath(when that setting is configured explicitly). This setting cannot end in a slash (/). -
server.compression.enabled - Set to
falseto disable HTTP compression for all responses. Default:true server.cors.enabled- Set to
trueto allow cross-origin API calls. Default:false. This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. server.cors.allowCredentials- Set to
trueto allow browser code to access response body whenever request performed with user credentials. Default:false. This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. server.cors.allowOriginStack- List of origins permitted to access resources. You must specify explicit hostnames and not use
server.cors.allowOrigin: ["*"]whenserver.cors.allowCredentials: true. Default: ["*"] server.compression.referrerWhitelist- 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
Refererheader. This setting may not be used whenserver.compression.enabledis set tofalse. Default:none server.compression.brotli.enabled-
Set to
trueto enable brotli (br) compression format.NoteBrowsers not supporting brotli compression will fallback to using gzip instead. This setting may not be used when
server.compression.enabledis set tofalse. Default:falseNoteIt is available in Elastic Cloud 8.6.0 and later versions.
-
server.securityResponseHeaders.strictTransportSecurity - Controls whether the
Strict-Transport-Securityheader is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are any text value ornull. To disable, set tonull. Default:null -
server.securityResponseHeaders.xContentTypeOptions - Controls whether the
X-Content-Type-Optionsheader is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values arenosniffornull. To disable, set tonull. Default:"nosniff" -
server.securityResponseHeaders.referrerPolicy - Controls whether the
Referrer-Policyheader is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values areno-referrer,no-referrer-when-downgrade,origin,origin-when-cross-origin,same-origin,strict-origin,strict-origin-when-cross-origin,unsafe-url, ornull. To disable, set tonull. Default:"strict-origin-when-cross-origin" -
server.securityResponseHeaders.permissionsPolicy - Controls whether the
Permissions-Policyheader is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are any text value ornull. Refer to thePermissions-Policydocumentation for defined directives, values, and text format. To disable, set tonull. Default:camera=(), display-capture=(), fullscreen=(self), geolocation=(), microphone=(), web-share=(). This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -
server.securityResponseHeaders.permissionsPolicyReportOnly - Controls whether the
Permissions-Policy-Report-Onlyheader is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values are any text value ornull. Refer to thePermissions-Policydocumentation for defined directives, values, and text format. This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. server.securityResponseHeaders.disableEmbedding- Controls whether the
Content-Security-PolicyandX-Frame-Optionsheaders are configured to disable embedding Kibana in other webpages using iframes. When set totrue, secure headers are used to disable embedding, which adds theframe-ancestors: 'self'directive to theContent-Security-Policyresponse header and adds theX-Frame-Options: SAMEORIGINresponse header. Default:false -
server.securityResponseHeaders.crossOriginOpenerPolicy - Controls whether the
Cross-Origin-Opener-Policyheader is used in all responses to the client from the Kibana server, and specifies what value is used. Allowed values areunsafe-none,same-origin-allow-popups,same-origin, ornull. To disable, set tonull. Default:"same-origin"It is available in Elastic Cloud 8.7.0 and later versions. server.customResponseHeaders- Header names and values to send on all responses to the client from the Kibana server. Default:
{} -
server.shutdownTimeout - Sets the grace period for Kibana to attempt to resolve any ongoing HTTP requests after receiving a
SIGTERM/SIGINTsignal, and before shutting down. Any new HTTP requests received during this period are rejected, because the incoming socket is closed without further processing. Default:30s -
server.host - 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.0to make Kibana listen on all IPs (public and private). Default:"localhost" server.keepaliveTimeout- The number of milliseconds to wait for additional data before restarting the
server.socketTimeoutcounter. Default:"120000" -
server.maxPayload - The maximum payload size in bytes for incoming server requests. Default:
1048576 server.name- A human-readable display name that identifies this Kibana instance. Default:
"your-hostname" -
server.port - Kibana is served by a back end server. This setting specifies the port to use. Default:
5601 -
server.protocol -
The HTTP protocol to use, either
http1orhttp2. Set tohttp1to opt out ofHTTP/2support when TLS is enabled. Use ofhttp1may impact browser loading performance especially for dashboards with many panels. Default:http2if TLS is enabled, otherwisehttp1. This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.NoteBy default, enabling
http2requires a validh2cconfiguration, meaning that TLS must be enabled viaserver.ssl.enabledandserver.ssl.supportedProtocols, if specified, must contain at leastTLSv1.2orTLSv1.3. Strict validation of theh2csetup can be disabled by addingserver.http2.allowUnsecure: trueto the configuration. -
server.rateLimiter.enabled -
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 Requestsstatus 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.
Default:
false server.rateLimiter.elu-
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 Requestsstatus 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.
server.rateLimiter.term-
This value is one of
short,medium, orlong, 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 to15s,30s, and60s, 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
mediumterm 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. -
server.requestId.allowFromAnyIp - Sets whether or not the
X-Opaque-Idheader should be trusted from any IP address for identifying requests in logs and forwarded to Elasticsearch. server.requestId.ipAllowlist- A list of IPv4 and IPv6 address which the
X-Opaque-Idheader 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.allowFromAnyIpmust also be set tofalse. -
server.rewriteBasePath - Specifies whether Kibana should rewrite requests that are prefixed with
server.basePathor require that they are rewritten by your reverse proxy. Default:false -
server.socketTimeout - The number of milliseconds to wait before closing an inactive socket. Default:
"120000" -
server.payloadTimeout - 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. Default:
"20000" -
server.ssl.certificateandserver.ssl.key -
Paths to a PEM-encoded X.509 server certificate and its corresponding private key. These are used by Kibana to establish trust when receiving inbound SSL/TLS connections from users.
NoteThese settings cannot be used in conjunction with
server.ssl.keystore.path. -
server.ssl.certificateAuthorities -
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.pathand/orserver.ssl.truststore.path. -
server.ssl.cipherSuites - Details on the format, and the valid options, are available via the OpenSSL cipher list format documentation. 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. server.ssl.clientAuthentication- 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. Default:"none" -
server.ssl.enabled - | 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 viaserver.ssl.keystore.pathor the combination ofserver.ssl.certificateandserver.ssl.key. Default:false server.ssl.keyPassphrase- The password that decrypts the private key that is specified via
server.ssl.key. This value is optional, as the key may not be encrypted. -
server.ssl.keystore.path -
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.certificateAuthoritiesand/orserver.ssl.truststore.path.NoteThis setting cannot be used in conjunction with
server.ssl.certificateorserver.ssl.key server.ssl.keystore.password- The password that will be used to decrypt the keystore specified via
server.ssl.keystore.path. If the keystore has no password, leave this unset. If the keystore has an empty password, set this to"". -
server.ssl.truststore.path -
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.certificateAuthoritiesand/orserver.ssl.keystore.path. server.ssl.truststore.password- The password that will be used to decrypt the trust store specified via
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"". server.ssl.redirectHttpFromPort- Kibana binds to this port and redirects all http requests to https over the port configured as
server.port. -
server.ssl.supportedProtocols - An array of supported protocols with versions. Valid protocols:
TLSv1,TLSv1.1,TLSv1.2,TLSv1.3. Default: TLSv1.2, TLSv1.3 EnablingTLSv1.1would require both setting the--tls-min-1.1option in thenode.optionsconfiguration and addingTLSv1.1toserver.ssl.supportedProtocols.HTTP/2requires the use of minimumTLSv1.2for secure connections. -
server.uuid - 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
datapath. -
server.xsrf.allowlist -
It is not recommended to disable protections for arbitrary API endpoints. Instead, supply the
kbn-xsrfheader. Theserver.xsrf.allowlistsetting requires the following format:*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.
-
server.xsrf.disableProtection - Setting this to
truewill completely disable Cross-site request forgery protection in Kibana. This is not recommended. Default:false status.allowAnonymous- If authentication is enabled, setting this to
trueenables unauthenticated users to access the Kibana server status API and status page. Default:false -
telemetry.allowChangingOptInStatus - When
false, users cannot change the opt-in status through Advanced Settings, and Kibana only looks at the value oftelemetry.optInto determine whether to send telemetry data or not. Default:true. -
telemetry.optIn -
Set to
falseto stop sending any telemetry data to Elastic. Reporting your cluster statistics helps us improve your user experience. Whenfalse, the telemetry data is never sent to Elastic.This setting can be changed at any time in Advanced Settings. To prevent users from changing it, set
telemetry.allowChangingOptInStatustofalse. Default:true unifiedSearch.autocomplete.valueSuggestions.timeout- Time in milliseconds to wait for autocomplete suggestions from Elasticsearch. This value must be a whole number greater than zero. Default:
"1000" unifiedSearch.autocomplete.valueSuggestions.terminateAfter-
Maximum number of documents loaded by each shard to generate autocomplete suggestions. This value must be a whole number greater than zero. Default:
"100000"NoteTo reload the logging settings, send a SIGHUP signal to Kibana. For more logging configuration options, see the Configure Logging in Kibana guide.
vis_type_table.legacyVisEnabled- Starting from version 7.11, a new datatable visualization is used. Set to
trueto enable the legacy version. In version 8.0 and later, the old implementation is removed and this setting is no longer supported. vis_type_vega.enable- For 7.7 version and later, set to
falseto disable Vega vizualizations. Default:true vega.enableExternalUrls- Set to
trueto allow Vega vizualizations to use data from sources other than the linked Elasticsearch cluster. In version 8.0 and later, thevega.enableExternalUrlsis not supported. Usevis_type_vega.enableExternalUrlsinstead. vis_type_vega.enableExternalUrls- 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. Default:
false xpack.ccr.ui.enabled- Set this value to false to disable the Cross-Cluster Replication UI. Default:
true -
xpack.discoverEnhanced.actions.exploreDataInContextMenu.enabled -
Enables the Explore underlying data option that allows you to open Discover from a dashboard panel and view the panel data. Default:
falseWhen 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.
-
xpack.discoverEnhanced.actions.exploreDataInChart.enabled - Enables you to view the underlying documents in a data series from a dashboard panel. Default:
false xpack.ilm.ui.enabled- Set this value to false to disable the Index Lifecycle Policies UI. Default:
true xpack.index_management.ui.enabled- Set this value to false to disable the Index Management UI. Default:
true xpack.license_management.ui.enabled- Set this value to false to disable the License Management UI. Default:
true xpack.remote_clusters.ui.enabled- Set this value to false to disable the Remote Clusters UI. Default:
true xpack.rollup.ui.enabled-
Set this value to false to disable the Rollup Jobs UI. Default: true
Deprecated in 8.11.0.Rollups are deprecated and will be removed in a future version. Use downsampling instead.
xpack.securitySolution.maxUploadResponseActionFileBytes-
Allow to configure the max file upload size for use with the Upload File Repsonse action available with the Defend Integration. To learn more, check Endpoint Response actions. It is available in Elastic Cloud 8.9.0 and later versions.
xpack.snapshot_restore.ui.enabled- Set this value to false to disable the Snapshot and Restore UI. Default: true
xpack.upgrade_assistant.ui.enabled- Set this value to false to disable the Upgrade Assistant UI. Default: true