mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
[7.7] [DOCS] Reformats the Configure Kibana settings tables into definition lists (#132531) (#133661)
* [DOCS] Reformats the Configure Kibana settings tables into definition lists (#132531)
* [DOCS] Reformats the Configure Kibana settings tables into definition lists
* Review comments
(cherry picked from commit ae7bfaca54)
* Fixes broken link
This commit is contained in:
Kaarina Tungseth
GitHub
parent
da559bc714
commit
cc43e9871d
1 changed files with 229 additions and 304 deletions
|
|
@ -11,132 +11,113 @@ The default host and port settings configure {kib} to run on `localhost:5601`. T
|
|||
variety of other options. Finally, environment variables can be injected into
|
||||
configuration using `${MY_ENV_VAR}` syntax.
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `console.enabled:`
|
||||
| Toggling this causes the server to regenerate assets on the next startup,
|
||||
`console.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 `false` to disable Console. *Default: `true`*
|
||||
|
||||
| `cpu.cgroup.path.override:`
|
||||
| Override for cgroup cpu path when mounted in a
|
||||
`cpu.cgroup.path.override`::
|
||||
Override for cgroup cpu path when mounted in a
|
||||
manner that is inconsistent with `/proc/self/cgroup`.
|
||||
|
||||
| `cpuacct.cgroup.path.override:`
|
||||
| Override for cgroup cpuacct path when mounted
|
||||
`cpuacct.cgroup.path.override`::
|
||||
Override for cgroup cpuacct path when mounted
|
||||
in a manner that is inconsistent with `/proc/self/cgroup`.
|
||||
|
||||
| `csp.rules:`
|
||||
| A https://w3c.github.io/webappsec-csp/[content-security-policy] template
|
||||
`csp.rules`::
|
||||
A https://w3c.github.io/webappsec-csp/[content-security-policy] template
|
||||
that disables certain unnecessary and potentially insecure capabilities in
|
||||
the browser. It is strongly recommended that you keep the default CSP rules
|
||||
that ship with {kib}.
|
||||
|
||||
| `csp.strict:`
|
||||
| Blocks {kib} access to any browser that
|
||||
[[csp-strict]] `csp.strict`::
|
||||
Blocks {kib} 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.
|
||||
For more information, refer to <<csp-strict-mode, Content Security Policy>>.
|
||||
*Default: `true`*
|
||||
|
||||
| `csp.warnLegacyBrowsers:`
|
||||
| Shows a warning message after loading {kib} to any browser that does not
|
||||
`csp.warnLegacyBrowsers`::
|
||||
Shows a warning message after loading {kib} to any browser that does not
|
||||
enforce even rudimentary CSP rules, though {kib} is still accessible. This
|
||||
configuration is effectively ignored when `csp.strict` is enabled.
|
||||
*Default: `true`*
|
||||
|
||||
| `elasticsearch.customHeaders:`
|
||||
| Header names and values to send to {es}. Any custom headers cannot be
|
||||
`elasticsearch.customHeaders`::
|
||||
Header names and values to send to {es}. Any custom headers cannot be
|
||||
overwritten by client-side headers, regardless of the
|
||||
`elasticsearch.requestHeadersWhitelist` configuration. *Default: `{}`*
|
||||
|
||||
| `elasticsearch.hosts:`
|
||||
| The URLs of the {es} instances to use for all your queries. All nodes
|
||||
[[elasticsearch-hosts]] `elasticsearch.hosts`::
|
||||
The URLs of the {es} 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 {es}, use the `https` protocol
|
||||
in this setting.
|
||||
|
||||
| `elasticsearch.logQueries:`
|
||||
| Log queries sent to {es}. Requires `logging.verbose` set to `true`.
|
||||
`elasticsearch.logQueries`::
|
||||
Log queries sent to {es}. Requires `logging.verbose` set to `true`.
|
||||
This is useful for seeing the query DSL generated by applications that
|
||||
currently do not have an inspector, for example Timelion and Monitoring.
|
||||
*Default: `false`*
|
||||
|
||||
| `elasticsearch.pingTimeout:`
|
||||
| Time in milliseconds to wait for {es} to respond to pings.
|
||||
`elasticsearch.pingTimeout`::
|
||||
Time in milliseconds to wait for {es} to respond to pings.
|
||||
*Default: the value of the `elasticsearch.requestTimeout` setting*
|
||||
|
||||
| `elasticsearch.preserveHost:`
|
||||
| When the value is `true`, {kib} uses the hostname specified in the
|
||||
`elasticsearch.preserveHost`::
|
||||
When the value is `true`, {kib} uses the hostname specified in the
|
||||
`server.host` setting. When the value is `false`, {kib} uses
|
||||
the hostname of the host that connects to this {kib} instance. *Default: `true`*
|
||||
|
||||
| `elasticsearch.requestHeadersWhitelist:`
|
||||
| List of {kib} client-side headers to send to {es}. To send *no* client-side
|
||||
[[elasticsearch-requestHeadersWhitelist]] `elasticsearch.requestHeadersWhitelist`::
|
||||
List of {kib} client-side headers to send to {es}. 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, basic authentication>> in {kib}.
|
||||
*Default: `[ 'authorization' ]`*
|
||||
|
||||
| `elasticsearch.requestTimeout:`
|
||||
| Time in milliseconds to wait for responses from the back end or {es}.
|
||||
[[elasticsearch-requestTimeout]] `elasticsearch.requestTimeout`::
|
||||
Time in milliseconds to wait for responses from the back end or {es}.
|
||||
This value must be a positive integer. *Default: `30000`*
|
||||
|
||||
| `elasticsearch.shardTimeout:`
|
||||
| Time in milliseconds for {es} to wait for responses from shards.
|
||||
`elasticsearch.shardTimeout`::
|
||||
Time in milliseconds for {es} to wait for responses from shards.
|
||||
Set to 0 to disable. *Default: `30000`*
|
||||
|
||||
| `elasticsearch.sniffInterval:`
|
||||
| Time in milliseconds between requests to check {es} for an updated list of
|
||||
`elasticsearch.sniffInterval`::
|
||||
Time in milliseconds between requests to check {es} for an updated list of
|
||||
nodes. *Default: `false`*
|
||||
|
||||
| `elasticsearch.sniffOnStart:`
|
||||
| Attempt to find other {es} nodes on startup. *Default: `false`*
|
||||
`elasticsearch.sniffOnStart`::
|
||||
Attempt to find other {es} nodes on startup. *Default: `false`*
|
||||
|
||||
| `elasticsearch.sniffOnConnectionFault:`
|
||||
| Update the list of {es} nodes immediately following a connection fault.
|
||||
`elasticsearch.sniffOnConnectionFault`::
|
||||
Update the list of {es} nodes immediately following a connection fault.
|
||||
*Default: `false`*
|
||||
|
||||
| `elasticsearch.ssl.alwaysPresentCertificate:`
|
||||
| Controls {kib} behavior in regard to presenting a client certificate when
|
||||
[[elasticsearch-ssl-alwaysPresentCertificate]] `elasticsearch.ssl.alwaysPresentCertificate`::
|
||||
Controls {kib} behavior in regard to presenting a client certificate when
|
||||
requested by {es}. This setting applies to all outbound SSL/TLS connections
|
||||
to {es}, including requests that are proxied for end users. *Default: `false`*
|
||||
|
||||
|===
|
||||
|
||||
[WARNING]
|
||||
============
|
||||
When {es} uses certificates to authenticate end users with a PKI realm
|
||||
and `elasticsearch.ssl.alwaysPresentCertificate` is `true`,
|
||||
+
|
||||
WARNING: When {es} 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 {kib}
|
||||
server.
|
||||
============
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `elasticsearch.ssl.certificate:` and `elasticsearch.ssl.key:`
|
||||
| Paths to a PEM-encoded X.509 client certificate and its corresponding
|
||||
[[elasticsearch-ssl-cert-key]] `elasticsearch.ssl.certificate` and `elasticsearch.ssl.key`::
|
||||
Paths to a PEM-encoded X.509 client certificate and its corresponding
|
||||
private key. These are used by {kib} to authenticate itself when making
|
||||
outbound SSL/TLS connections to {es}. For this setting to take effect, the
|
||||
`xpack.security.http.ssl.client_authentication` setting in {es} must be also
|
||||
be set to `"required"` or `"optional"` to request a client certificate from
|
||||
{kib}.
|
||||
+
|
||||
NOTE: These settings cannot be used in conjunction with `elasticsearch.ssl.keystore.path`.
|
||||
|
||||
|===
|
||||
|
||||
[NOTE]
|
||||
============
|
||||
These settings cannot be used in conjunction with `elasticsearch.ssl.keystore.path`.
|
||||
============
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `elasticsearch.ssl.certificateAuthorities:`
|
||||
| Paths to one or more PEM-encoded X.509 certificate authority (CA)
|
||||
[[elasticsearch-ssl-certificateAuthorities]] `elasticsearch.ssl.certificateAuthorities`::
|
||||
Paths to one or more PEM-encoded X.509 certificate authority (CA)
|
||||
certificates, which make up a trusted certificate chain for {es}. This chain is
|
||||
used by {kib} to establish trust when making outbound SSL/TLS connections to
|
||||
{es}.
|
||||
|
|
@ -144,13 +125,13 @@ used by {kib} to establish trust when making outbound SSL/TLS connections to
|
|||
In addition to this setting, trusted certificates may be specified via
|
||||
`elasticsearch.ssl.keystore.path` and/or `elasticsearch.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
|
||||
`elasticsearch.ssl.keyPassphrase`::
|
||||
The password that decrypts the private key that is specified
|
||||
via <<elasticsearch-ssl-cert-key, `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
|
||||
[[elasticsearch-ssl-keystore-path]] `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 {kib} to authenticate itself when
|
||||
making outbound SSL/TLS connections to {es}. For this setting, you must also set
|
||||
the `xpack.security.http.ssl.client_authentication` setting in {es} to
|
||||
|
|
@ -160,28 +141,20 @@ If the keystore contains any additional certificates, they are used as a
|
|||
trusted certificate chain for {es}. This chain is used by {kib} to establish
|
||||
trust when making outbound SSL/TLS connections to {es}. In addition to this
|
||||
setting, trusted certificates may be specified via
|
||||
`elasticsearch.ssl.certificateAuthorities` and/or
|
||||
`elasticsearch.ssl.truststore.path`.
|
||||
<<elasticsearch-ssl-certificateAuthorities, `elasticsearch.ssl.certificateAuthorities`>> and/or
|
||||
<<elasticsearch-ssl-truststore-path, `elasticsearch.ssl.truststore.path`>>.
|
||||
+
|
||||
NOTE: This setting cannot be used in conjunction with
|
||||
<<elasticsearch-ssl-cert-key, `elasticsearch.ssl.certificate`>> or <<elasticsearch-ssl-cert-key, `elasticsearch.ssl.key`>>.
|
||||
|
||||
|===
|
||||
|
||||
[NOTE]
|
||||
============
|
||||
This setting cannot be used in conjunction with
|
||||
`elasticsearch.ssl.certificate` or `elasticsearch.ssl.key`.
|
||||
============
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `elasticsearch.ssl.keystore.password:`
|
||||
| The password that decrypts the keystore specified via
|
||||
`elasticsearch.ssl.keystore.path`. If the keystore has no password, leave this
|
||||
`elasticsearch.ssl.keystore.password`::
|
||||
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
|
||||
`""`.
|
||||
|
||||
| `elasticsearch.ssl.truststore.path:`::
|
||||
| Path to a PKCS#12 trust store that contains one or more X.509 certificate
|
||||
[[elasticsearch-ssl-truststore-path]] `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
|
||||
{es}. This chain is used by {kib} to establish trust when making outbound
|
||||
SSL/TLS connections to {es}.
|
||||
|
|
@ -190,82 +163,72 @@ In addition to this setting, trusted certificates may be specified via
|
|||
`elasticsearch.ssl.certificateAuthorities` and/or
|
||||
`elasticsearch.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.truststore.password`::
|
||||
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 `""`.
|
||||
|
||||
| `elasticsearch.ssl.verificationMode:`
|
||||
| Controls the verification of the server certificate that {kib} receives when
|
||||
[[elasticsearch-ssl-verificationMode]] `elasticsearch.ssl.verificationMode`::
|
||||
Controls the verification of the server certificate that {kib} receives when
|
||||
making an outbound SSL/TLS connection to {es}. 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.startupTimeout:`
|
||||
| Time in milliseconds to wait for {es} at {kib} startup before retrying.
|
||||
`elasticsearch.startupTimeout`::
|
||||
Time in milliseconds to wait for {es} at {kib} startup before retrying.
|
||||
*Default: `5000`*
|
||||
|
||||
| `elasticsearch.username:` and `elasticsearch.password:`
|
||||
| If your {es} is protected with basic authentication, these settings provide
|
||||
[[elasticsearch-user-passwd]] `elasticsearch.username` and `elasticsearch.password`::
|
||||
If your {es} is protected with basic authentication, these settings provide
|
||||
the username and password that the {kib} server uses to perform maintenance
|
||||
on the {kib} index at startup. {kib} users still need to authenticate with
|
||||
{es}, which is proxied through the {kib} server.
|
||||
|
||||
| `interpreter.enableInVisualize`
|
||||
| Enables use of interpreter in Visualize. *Default: `true`*
|
||||
`interpreter.enableInVisualize`::
|
||||
Enables use of interpreter in Visualize. *Default: `true`*
|
||||
|
||||
| `kibana.defaultAppId:`
|
||||
| The default application to load. *Default: `"home"`*
|
||||
`kibana.defaultAppId`::
|
||||
The default application to load. *Default: `"home"`*
|
||||
|
||||
| `kibana.index:`
|
||||
| {kib} uses an index in {es} to store saved searches, visualizations, and
|
||||
`kibana.index`::
|
||||
{kib} uses an index in {es} to store saved searches, visualizations, and
|
||||
dashboards. {kib} creates a new index if the index doesn’t already exist.
|
||||
If you configure a custom index, the name must be lowercase, and conform to the
|
||||
{es} {ref}/indices-create-index.html[index name limitations].
|
||||
*Default: `".kibana"`*
|
||||
|
||||
| `kibana.autocompleteTimeout:` {ess-icon}
|
||||
| Time in milliseconds to wait for autocomplete suggestions from {es}.
|
||||
`kibana.autocompleteTimeout` {ess-icon}::
|
||||
Time in milliseconds to wait for autocomplete suggestions from {es}.
|
||||
This value must be a whole number greater than zero. *Default: `"1000"`*
|
||||
|
||||
| `kibana.autocompleteTerminateAfter:` {ess-icon}
|
||||
| Maximum number of documents loaded by each shard to generate autocomplete
|
||||
`kibana.autocompleteTerminateAfter` {ess-icon}::
|
||||
Maximum number of documents loaded by each shard to generate autocomplete
|
||||
suggestions. This value must be a whole number greater than zero.
|
||||
*Default: `"100000"`*
|
||||
+
|
||||
NOTE: To reload the logging settings, send a SIGHUP signal to {kib}.
|
||||
|
||||
|===
|
||||
|
||||
[NOTE]
|
||||
============
|
||||
To reload the logging settings, send a SIGHUP signal to {kib}.
|
||||
============
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `logging.dest:`
|
||||
| Enables you to specify a file where {kib} stores log output.
|
||||
`logging.dest`::
|
||||
Enables you to specify a file where {kib} stores log output.
|
||||
*Default: `stdout`*
|
||||
|
||||
| `logging.json:`
|
||||
| Logs output as JSON. When set to `true`, the logs are formatted as JSON
|
||||
`logging.json`::
|
||||
Logs output as JSON. When set to `true`, the logs are formatted as JSON
|
||||
strings that include timestamp, log level, context, message text, and any other
|
||||
metadata that may be associated with the log message.
|
||||
When `logging.dest.stdout` is set, and there is no interactive terminal ("TTY"),
|
||||
this setting defaults to `true`. *Default: `false`*
|
||||
|
||||
| `logging.quiet:`
|
||||
| Set the value of this setting to `true` to suppress all logging output other
|
||||
`logging.quiet`::
|
||||
Set the value of this setting to `true` to suppress all logging output other
|
||||
than error messages. *Default: `false`*
|
||||
|
||||
| `logging.rotate:`
|
||||
| experimental[] Specifies the options for the logging rotate feature.
|
||||
`logging.rotate`::
|
||||
experimental[] Specifies the options for the logging rotate feature.
|
||||
When not defined, all the sub options defaults would be applied.
|
||||
The following example shows a valid logging rotate configuration:
|
||||
|
||||
|===
|
||||
|
||||
+
|
||||
[source,text]
|
||||
--
|
||||
logging.rotate:
|
||||
|
|
@ -274,57 +237,54 @@ The following example shows a valid logging rotate configuration:
|
|||
keepFiles: 10
|
||||
--
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `logging.rotate.enabled:`
|
||||
| experimental[] Set the value of this setting to `true` to
|
||||
`logging.rotate.enabled`::
|
||||
experimental[] Set the value of this setting to `true` to
|
||||
enable log rotation. If you do not have a `logging.dest` set that is different from `stdout`
|
||||
that feature would not take any effect. *Default: `false`*
|
||||
|
||||
| `logging.rotate.everyBytes:`
|
||||
| experimental[] The maximum size of a log file (that is `not an exact` limit). After the
|
||||
`logging.rotate.everyBytes`::
|
||||
experimental[] The maximum size of a log file (that is `not an exact` limit). After the
|
||||
limit is reached, a new log file is generated. The default size limit is 10485760 (10 MB) and
|
||||
this option should be in the range of 1048576 (1 MB) to 1073741824 (1 GB). *Default: `10485760`*
|
||||
|
||||
| `logging.rotate.keepFiles:`
|
||||
| experimental[] The number of most recent rotated log files to keep
|
||||
`logging.rotate.keepFiles`::
|
||||
experimental[] The number of most recent rotated log files to keep
|
||||
on disk. Older files are deleted during log rotation. The default value is 7. The `logging.rotate.keepFiles`
|
||||
option has to be in the range of 2 to 1024 files. *Default: `7`*
|
||||
|
||||
| `logging.rotate.pollingInterval:`
|
||||
| experimental[] The number of milliseconds for the polling strategy in case
|
||||
`logging.rotate.pollingInterval`::
|
||||
experimental[] The number of milliseconds for the polling strategy in case
|
||||
the `logging.rotate.usePolling` is enabled. `logging.rotate.usePolling` must be in the 5000 to 3600000 millisecond range. *Default: `10000`*
|
||||
|
||||
| `logging.rotate.usePolling:`
|
||||
| experimental[] By default we try to understand the best way to monitoring
|
||||
`logging.rotate.usePolling`::
|
||||
experimental[] By default we try to understand the best way to monitoring
|
||||
the log file and warning about it. Please be aware there are some systems where watch api is not accurate. In those cases, in order to get the feature working,
|
||||
the `polling` method could be used enabling that option. *Default: `false`*
|
||||
|
||||
| `logging.silent:`
|
||||
| Set the value of this setting to `true` to
|
||||
`logging.silent`::
|
||||
Set the value of this setting to `true` to
|
||||
suppress all logging output. *Default: `false`*
|
||||
|
||||
| `logging.timezone`
|
||||
| Set to the canonical timezone ID
|
||||
`logging.timezone`::
|
||||
Set to the canonical timezone ID
|
||||
(for example, `America/Los_Angeles`) to log events using that timezone. For a
|
||||
list of timezones, refer to https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. *Default: `UTC`*
|
||||
|
||||
| [[logging-verbose]] `logging.verbose:` {ece-icon}
|
||||
| Set to `true` to log all events, including system usage information and all
|
||||
[[logging-verbose]] `logging.verbose` {ece-icon}::
|
||||
Set to `true` to log all events, including system usage information and all
|
||||
requests. *Default: `false`*
|
||||
|
||||
| `map.includeElasticMapsService:` {ess-icon}
|
||||
| Set to `false` to disable connections to Elastic Maps Service.
|
||||
`map.includeElasticMapsService` {ess-icon}::
|
||||
Set to `false` to disable connections to Elastic Maps Service.
|
||||
When `includeElasticMapsService` is turned off, only the vector layers configured by `map.regionmap`
|
||||
and the tile layer configured by `map.tilemap.url` are available in <<maps, Maps>>. *Default: `true`*
|
||||
|
||||
| `map.proxyElasticMapsServiceInMaps:`
|
||||
| Set to `true` to proxy all <<maps, Maps application>> Elastic Maps Service
|
||||
`map.proxyElasticMapsServiceInMaps`::
|
||||
Set to `true` to proxy all <<maps, Maps application>> Elastic Maps Service
|
||||
requests through the {kib} server. *Default: `false`*
|
||||
|
||||
| [[regionmap-settings]] `map.regionmap:` {ess-icon} {ece-icon}
|
||||
| Specifies additional vector layers for
|
||||
[[regionmap-settings]] `map.regionmap` {ess-icon} {ece-icon}::
|
||||
Specifies additional vector layers for
|
||||
use in <<maps, Maps>> visualizations. Each layer
|
||||
object points to an external vector file that contains a geojson
|
||||
FeatureCollection. The file must use the
|
||||
|
|
@ -332,9 +292,7 @@ https://en.wikipedia.org/wiki/World_Geodetic_System[WGS84 coordinate reference s
|
|||
and only include polygons. If the file is hosted on a separate domain from
|
||||
{kib}, the server needs to be CORS-enabled so {kib} can download the file.
|
||||
The following example shows a valid region map configuration.
|
||||
|
||||
|===
|
||||
|
||||
+
|
||||
[source,text]
|
||||
--
|
||||
map.regionmap:
|
||||
|
|
@ -350,26 +308,21 @@ map.regionmap:
|
|||
description: "INSEE numeric identifier"
|
||||
--
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| [[regionmap-ES-map]] `map.includeElasticMapsService:` {ece-icon}
|
||||
| Turns on or off whether layers from the Elastic Maps Service should be included in the vector
|
||||
[[regionmap-ES-map]] `map.includeElasticMapsService` {ece-icon}::
|
||||
Turns on or off whether layers from the Elastic Maps Service should be included in the vector
|
||||
layer option list. By turning this off,
|
||||
only the layers that are configured here will be included. The default is `true`.
|
||||
This also affects whether tile-service from the Elastic Maps Service will be available.
|
||||
|
||||
| [[regionmap-attribution]] `map.regionmap.layers[].attribution:` {ess-icon} {ece-icon}
|
||||
| Optional. References the originating source of the geojson file.
|
||||
[[regionmap-attribution]] `map.regionmap.layers[].attribution` {ess-icon} {ece-icon}::
|
||||
Optional. References the originating source of the geojson file.
|
||||
|
||||
| [[regionmap-fields]] `map.regionmap.layers[].fields[]:` {ess-icon} {ece-icon}
|
||||
| Mandatory. Each layer
|
||||
[[regionmap-fields]] `map.regionmap.layers[].fields[]` {ess-icon} {ece-icon}::
|
||||
Mandatory. Each layer
|
||||
can contain multiple fields to indicate what properties from the geojson
|
||||
features you wish to expose. The following shows how to define multiple
|
||||
properties:
|
||||
|
||||
|===
|
||||
|
||||
+
|
||||
[source,text]
|
||||
--
|
||||
map.regionmap:
|
||||
|
|
@ -385,264 +338,236 @@ map.regionmap:
|
|||
description: "INSEE numeric identifier"
|
||||
--
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| [[regionmap-field-description]] `map.regionmap.layers[].fields[].description:` {ess-icon} {ece-icon}
|
||||
| Mandatory. The human readable text that is shown under the Options tab when
|
||||
[[regionmap-field-description]] `map.regionmap.layers[].fields[].description` {ess-icon} {ece-icon}::
|
||||
Mandatory. The human readable text that is shown under the Options tab when
|
||||
building the Region Map visualization.
|
||||
|
||||
| [[regionmap-field-name]] `map.regionmap.layers[].fields[].name:` {ess-icon} {ece-icon}
|
||||
| Mandatory.
|
||||
This value is used to do an inner-join between the document stored in
|
||||
[[regionmap-field-name]] `map.regionmap.layers[].fields[].name` {ess-icon} {ece-icon}::
|
||||
Mandatory. This value is used to do an inner-join between the document stored in
|
||||
{es} and the geojson file. For example, if the field in the geojson is
|
||||
called `Location` and has city names, there must be a field in {es}
|
||||
that holds the same values that {kib} can then use to lookup for the geoshape
|
||||
data.
|
||||
|
||||
| [[regionmap-name]] `map.regionmap.layers[].name:` {ess-icon} {ece-icon}
|
||||
| Mandatory. A description of
|
||||
[[regionmap-name]] `map.regionmap.layers[].name` {ess-icon} {ece-icon}::
|
||||
Mandatory. A description of
|
||||
the map being provided.
|
||||
|
||||
| [[regionmap-url]] `map.regionmap.layers[].url:` {ess-icon} {ece-icon}
|
||||
| Mandatory. The location of the
|
||||
[[regionmap-url]] `map.regionmap.layers[].url` {ess-icon} {ece-icon}::
|
||||
Mandatory. The location of the
|
||||
geojson file as provided by a webserver.
|
||||
|
||||
| [[tilemap-settings]] `map.tilemap.options.attribution:` {ess-icon} {ece-icon}
|
||||
| The map attribution string.
|
||||
[[tilemap-settings]] `map.tilemap.options.attribution` {ess-icon} {ece-icon}::
|
||||
The map attribution string.
|
||||
*Default: `"© [Elastic Maps Service](https://www.elastic.co/elastic-maps-service)"`*
|
||||
|
||||
| [[tilemap-max-zoom]] `map.tilemap.options.maxZoom:` {ess-icon} {ece-icon}
|
||||
| The maximum zoom level. *Default: `10`*
|
||||
[[tilemap-max-zoom]] `map.tilemap.options.maxZoom` {ess-icon} {ece-icon}::
|
||||
The maximum zoom level. *Default: `10`*
|
||||
|
||||
| [[tilemap-min-zoom]] `map.tilemap.options.minZoom:` {ess-icon} {ece-icon}
|
||||
| The minimum zoom level. *Default: `1`*
|
||||
[[tilemap-min-zoom]] `map.tilemap.options.minZoom` {ess-icon} {ece-icon}::
|
||||
The minimum zoom level. *Default: `1`*
|
||||
|
||||
| [[tilemap-subdomains]] `map.tilemap.options.subdomains:` {ess-icon} {ece-icon}
|
||||
| An array of subdomains
|
||||
[[tilemap-subdomains]] `map.tilemap.options.subdomains` {ess-icon} {ece-icon}::
|
||||
An array of subdomains
|
||||
used by the tile service. Specify the position of the subdomain the URL with
|
||||
the token `{s}`.
|
||||
|
||||
| [[tilemap-url]] `map.tilemap.url:` {ess-icon} {ece-icon}
|
||||
| The URL to the tileservice that {kib} uses
|
||||
[[tilemap-url]] `map.tilemap.url` {ess-icon} {ece-icon}::
|
||||
The URL to the tileservice that {kib} uses
|
||||
to display map tiles in tilemap visualizations. By default,
|
||||
{kib} reads this URL from an external metadata service, but users can
|
||||
override this parameter to use 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"`
|
||||
|
||||
| `newsfeed.enabled:`
|
||||
| Controls whether to enable the newsfeed
|
||||
`newsfeed.enabled`::
|
||||
Controls whether to enable the newsfeed
|
||||
system for the {kib} UI notification center. Set to `false` to disable the
|
||||
newsfeed system. *Default: `true`*
|
||||
|
||||
| `path.data:`
|
||||
| The path where {kib} stores persistent data
|
||||
`path.data`::
|
||||
The path where {kib} stores persistent data
|
||||
not saved in {es}. *Default: `data`*
|
||||
|
||||
| `pid.file:`
|
||||
| Specifies the path where {kib} creates the process ID file.
|
||||
`pid.file`::
|
||||
Specifies the path where {kib} creates the process ID file.
|
||||
|
||||
| `ops.interval:`
|
||||
| Set the interval in milliseconds to sample
|
||||
`ops.interval`::
|
||||
Set the interval in milliseconds to sample
|
||||
system and process performance metrics. The minimum value is 100. *Default: `5000`*
|
||||
|
||||
| `server.basePath:`
|
||||
| Enables you to specify a path to mount {kib} at if you are
|
||||
running behind a proxy. Use the `server.rewriteBasePath` setting to tell {kib}
|
||||
[[server-basePath]] `server.basePath`::
|
||||
Enables you to specify a path to mount {kib} at if you are
|
||||
running behind a proxy. Use the <<server-rewriteBasePath, `server.rewriteBasePath`>> setting to tell {kib}
|
||||
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-compression]] `server.compression.enabled:`
|
||||
| Set to `false` to disable HTTP compression for all responses. *Default: `true`*
|
||||
[[server-compression]] `server.compression.enabled`::
|
||||
Set to `false` to disable HTTP compression for all responses. *Default: `true`*
|
||||
|
||||
| `server.compression.referrerWhitelist:`
|
||||
| Specifies an array of trusted hostnames, such as the {kib} host, or a reverse
|
||||
`server.compression.referrerWhitelist`::
|
||||
Specifies an array of trusted hostnames, such as the {kib} 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` is set to `false`. *Default: `none`*
|
||||
This setting may not be used when <<server-compression, `server.compression.enabled`>> is set to `false`. *Default: `none`*
|
||||
|
||||
| `server.customResponseHeaders:` {ess-icon}
|
||||
| Header names and values to
|
||||
send on all responses to the client from the {kib} server. *Default: `{}`*
|
||||
`server.customResponseHeaders` {ess-icon}::
|
||||
Header names and values to send on all responses to the client from the {kib} server. *Default: `{}`*
|
||||
|
||||
| `server.host:`
|
||||
| This setting specifies the host of the
|
||||
`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 {kib} server. *Default: `"localhost"`*
|
||||
|
||||
| `server.keepaliveTimeout:`
|
||||
| The number of milliseconds to wait for additional data before restarting
|
||||
`server.keepaliveTimeout`::
|
||||
The number of milliseconds to wait for additional data before restarting
|
||||
the `server.socketTimeout` counter. *Default: `"120000"`*
|
||||
|
||||
| `server.maxPayloadBytes:`
|
||||
| The maximum payload size in bytes
|
||||
`server.maxPayloadBytes`::
|
||||
The maximum payload size in bytes
|
||||
for incoming server requests. *Default: `1048576`*
|
||||
|
||||
| `server.name:`
|
||||
| A human-readable display name that
|
||||
`server.name`::
|
||||
A human-readable display name that
|
||||
identifies this {kib} instance. *Default: `"your-hostname"`*
|
||||
|
||||
| `server.port:`
|
||||
| {kib} is served by a back end server. This
|
||||
[[server-port]] `server.port`::
|
||||
{kib} is served by a back end server. This
|
||||
setting specifies the port to use. *Default: `5601`*
|
||||
|
||||
| `server.rewriteBasePath:`
|
||||
| Specifies whether {kib} should
|
||||
rewrite requests that are prefixed with `server.basePath` or require that they
|
||||
[[server-rewriteBasePath]] `server.rewriteBasePath`::
|
||||
Specifies whether {kib} should
|
||||
rewrite requests that are prefixed with <<server-basePath, `server.basePath`>> or require that they
|
||||
are rewritten by your reverse proxy. In {kib} 6.3 and earlier, the default is
|
||||
`false`. In {kib} 7.x, the setting is deprecated. In {kib} 8.0 and later, the
|
||||
default is `true`. *Default: `deprecated`*
|
||||
|
||||
| `server.socketTimeout:`
|
||||
| The number of milliseconds to wait before closing an
|
||||
[[server-socketTimeout]] `server.socketTimeout`::
|
||||
The number of milliseconds to wait before closing an
|
||||
inactive socket. *Default: `"120000"`*
|
||||
|
||||
| `server.ssl.certificate:` and `server.ssl.key:`
|
||||
| Paths to a PEM-encoded X.509 server certificate and its corresponding private key. These
|
||||
[[server-ssl-cert-key]] `server.ssl.certificate` and `server.ssl.key`::
|
||||
Paths to a PEM-encoded X.509 server certificate and its corresponding private key. These
|
||||
are used by {kib} to establish trust when receiving inbound SSL/TLS connections from users.
|
||||
+
|
||||
NOTE: These settings cannot be used in conjunction with <<server-ssl-keystore-path, `server.ssl.keystore.path`>>.
|
||||
|
||||
|===
|
||||
|
||||
[NOTE]
|
||||
============
|
||||
These settings cannot be used in conjunction with `server.ssl.keystore.path`.
|
||||
============
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `server.ssl.certificateAuthorities:`
|
||||
| Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates which make up a
|
||||
[[server-ssl-certificateAuthorities]] `server.ssl.certificateAuthorities`::
|
||||
Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates which make up a
|
||||
trusted certificate chain for {kib}. This chain is used by {kib} to establish trust when receiving inbound SSL/TLS connections from end
|
||||
users. If PKI authentication is enabled, this chain is also used by {kib} to verify client certificates from end users.
|
||||
+
|
||||
In addition to this setting, trusted certificates may be specified via `server.ssl.keystore.path` and/or `server.ssl.truststore.path`.
|
||||
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`>>.
|
||||
|
||||
| `server.ssl.cipherSuites:`
|
||||
| Details on the format, and the valid options, are available via the
|
||||
https://www.openssl.org/docs/man1.0.2/apps/ciphers.html#CIPHER-LIST-FORMAT[OpenSSL cipher list format documentation].
|
||||
*Default: `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-cipherSuites]] `server.ssl.cipherSuites`::
|
||||
Details on the format, and the valid options, are available via the
|
||||
https://www.openssl.org/docs/man1.1.1/man1/ciphers.html#CIPHER-LIST-FORMAT[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 {kib} for requesting a certificate from client
|
||||
`server.ssl.clientAuthentication`::
|
||||
Controls the behavior in {kib} 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:`
|
||||
[[server-ssl-enabled]] `server.ssl.enabled`::
|
||||
| Enables SSL/TLS for inbound connections to {kib}. When set to `true`, a certificate and its
|
||||
corresponding private key must be provided. These can be specified via `server.ssl.keystore.path` or the combination of
|
||||
`server.ssl.certificate` and `server.ssl.key`. *Default: `false`*
|
||||
|
||||
| `server.ssl.keyPassphrase:`
|
||||
| The password that decrypts the private key that is specified via `server.ssl.key`. This value
|
||||
`server.ssl.keyPassphrase`::
|
||||
The password that decrypts the private key that is specified via <<server-ssl-cert-key, `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
|
||||
[[server-ssl-keystore-path]] `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 {kib}. All of these are used by {kib}
|
||||
to establish trust when receiving inbound SSL/TLS connections from end users. The certificate chain is also used by {kib} 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` and/or
|
||||
`server.ssl.truststore.path`.
|
||||
+
|
||||
NOTE: This setting cannot be used in conjunction with `server.ssl.certificate` or `server.ssl.key`
|
||||
|
||||
|===
|
||||
|
||||
[NOTE]
|
||||
============
|
||||
This setting cannot be used in conjunction with `server.ssl.certificate` or `server.ssl.key`
|
||||
============
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
|
||||
| `server.ssl.keystore.password:`
|
||||
| The password that will be used to decrypt the keystore specified via `server.ssl.keystore.path`. If the
|
||||
`server.ssl.keystore.password`::
|
||||
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 `""`.
|
||||
|
||||
| `server.ssl.truststore.path:`
|
||||
| Path to a PKCS#12 trust store that contains one or more X.509 certificate authority (CA) certificates which
|
||||
[[server-ssl-truststore-path]] `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 {kib}. This chain is used by {kib} to establish trust when receiving inbound SSL/TLS connections
|
||||
from end users. If PKI authentication is enabled, this chain is also used by {kib} to verify client certificates from end users.
|
||||
+
|
||||
In addition to this setting, trusted certificates may be specified via `server.ssl.certificateAuthorities` and/or
|
||||
`server.ssl.keystore.path`.
|
||||
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`>>.
|
||||
|
||||
| `server.ssl.truststore.password:`
|
||||
| The password that will be used to decrypt the trust store specified via `server.ssl.truststore.path`. If
|
||||
`server.ssl.truststore.password`::
|
||||
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 `""`.
|
||||
|
||||
| `server.ssl.redirectHttpFromPort:`
|
||||
| {kib} binds to this port and redirects
|
||||
all http requests to https over the port configured as `server.port`.
|
||||
`server.ssl.redirectHttpFromPort`::
|
||||
{kib} binds to this port and redirects
|
||||
all http requests to https over the port configured as <<server-port, `server.port`>>.
|
||||
|
||||
| `server.ssl.supportedProtocols:`
|
||||
| An array of supported protocols with versions.
|
||||
Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`. *Default: TLSv1.1, TLSv1.2*
|
||||
[[server-ssl-supportedProtocols]] `server.ssl.supportedProtocols`::
|
||||
An array of supported protocols with versions.
|
||||
Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`, `TLSv1.3`. *Default: TLSv1.1, TLSv1.2, TLSv1.3*
|
||||
|
||||
|[[server-uuid]] `server.uuid:`
|
||||
| The unique identifier for this {kib} instance. It must be a valid UUIDv4. It gets automatically generated on the first startup if not specified and persisted in the `data` path.
|
||||
[[server-uuid]] `server.uuid`::
|
||||
The unique identifier for this {kib} instance. It must be a valid UUIDv4. It gets automatically generated on the first startup if not specified and persisted in the `data` path.
|
||||
|
||||
| [[settings-xsrf-whitelist]] `server.xsrf.whitelist:`
|
||||
| It is not recommended to disable protections for
|
||||
[[settings-xsrf-whitelist]] `server.xsrf.whitelist`::
|
||||
It is not recommended to disable protections for
|
||||
arbitrary API endpoints. Instead, supply the `kbn-xsrf` header.
|
||||
The `server.xsrf.whitelist` setting requires the following format:
|
||||
|
||||
|===
|
||||
|
||||
+
|
||||
[source,text]
|
||||
----
|
||||
*Default: [ ]* An array of API endpoints which should be exempt from Cross-Site Request Forgery ("XSRF") protections.
|
||||
----
|
||||
|
||||
[cols="2*<"]
|
||||
|===
|
||||
[[settings-xsrf-disableProtection]] `server.xsrf.disableProtection`::
|
||||
Setting this to `true` will completely disable Cross-site request forgery protection in Kibana. This is not recommended. *Default: `false`*
|
||||
|
||||
| [[settings-xsrf-disableProtection]] `server.xsrf.disableProtection:`
|
||||
| Setting this to `true` will completely disable Cross-site request forgery protection in Kibana. This is not recommended. *Default: `false`*
|
||||
|
||||
| `status.allowAnonymous:`
|
||||
| If authentication is enabled,
|
||||
`status.allowAnonymous`::
|
||||
If authentication is enabled,
|
||||
setting this to `true` enables unauthenticated users to access the {kib}
|
||||
server status API and status page. *Default: `false`*
|
||||
|
||||
| `telemetry.allowChangingOptInStatus`
|
||||
| When `true`, users are able to change the telemetry setting at a later time in
|
||||
[[telemetry-allowChangingOptInStatus]] `telemetry.allowChangingOptInStatus`::
|
||||
When `true`, users are able to change the telemetry setting at a later time in
|
||||
<<advanced-options, Advanced Settings>>. When `false`,
|
||||
{kib} looks at the value of `telemetry.optIn` to determine whether to send
|
||||
telemetry data or not. `telemetry.allowChangingOptInStatus` and `telemetry.optIn`
|
||||
cannot be `false` at the same time. *Default: `true`*.
|
||||
|
||||
| `telemetry.optIn`
|
||||
| When `true`, telemetry data is sent to Elastic.
|
||||
[[settings-telemetry-optIn]] `telemetry.optIn`::
|
||||
When `true`, telemetry data is sent to Elastic.
|
||||
When `false`, collection of telemetry data is disabled.
|
||||
To enable telemetry and prevent users from disabling it,
|
||||
set `telemetry.allowChangingOptInStatus` to `false` and `telemetry.optIn` to `true`.
|
||||
*Default: `true`*
|
||||
|
||||
| `telemetry.enabled`
|
||||
| Reporting your cluster statistics helps
|
||||
`telemetry.enabled`::
|
||||
Reporting your cluster statistics helps
|
||||
us improve your user experience. Your data is never shared with anyone. Set to
|
||||
`false` to disable telemetry capabilities entirely. You can alternatively opt
|
||||
out through *Advanced Settings*. *Default: `true`*
|
||||
|
||||
| `vis_type_vega.enableExternalUrls:` {ess-icon}
|
||||
| Set this value to true to allow Vega to use any URL to access external data
|
||||
`vis_type_vega.enableExternalUrls` {ess-icon}::
|
||||
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 {es}. *Default: `false`*
|
||||
|
||||
| `xpack.license_management.enabled`
|
||||
| Set this value to false to
|
||||
`xpack.license_management.enabled`::
|
||||
Set this value to false to
|
||||
disable the License Management UI. *Default: `true`*
|
||||
|
||||
| `xpack.rollup.enabled:`
|
||||
| Set this value to false to disable the
|
||||
`xpack.rollup.enabled`::
|
||||
Set this value to false to disable the
|
||||
Rollup UI. *Default: true*
|
||||
|
||||
| `i18n.locale` {ess-icon}
|
||||
| Set this value to change the {kib} interface language.
|
||||
`i18n.locale` {ess-icon}::
|
||||
Set this value to change the {kib} interface language.
|
||||
Valid locales are: `en`, `zh-CN`, `ja-JP`. *Default: `en`*
|
||||
|
||||
|===
|
||||
|
||||
include::{kib-repo-dir}/settings/alert-action-settings.asciidoc[]
|
||||
include::{kib-repo-dir}/settings/apm-settings.asciidoc[]
|
||||
include::{kib-repo-dir}/settings/dev-settings.asciidoc[]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue