WARNING: Version 5.2 of Kibana has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Settings Securing Console »
Elastic Docs ›Kibana User Guide [5.2] ›Console

Configuring Console

edit

Configuring Console

edit

You can add the following options in the config/kibana.yml file:

console.enabled
Default: true Set to false to disable Console. Toggling this will cause the server to regenerate assets on the next startup, which may cause a delay before pages start being served.
console.proxyFilter
Default: .* A list of regular expressions that are used to validate any outgoing request from Console. If none of these match, the request will be rejected. See Securing Console for more details.
console.proxyConfig

A list of configuration options that are based on the proxy target. Use this to set custom timeouts or SSL settings for specific hosts. This is done by defining a set of match criteria using wildcards/globs which will be checked against each request. The configuration from all matching rules will then be merged together to configure the proxy used for that request.

The valid match keys are match.protocol, match.host, match.port, and match.path. All of these keys default to *, which means they will match any value.

Example:

console.proxyConfig:
  - match:
      host: "*.internal.org" # allow any host that ends in .internal.org
      port: "{9200..9299}" # allow any port from 9200-9299

    ssl:
      ca: "/opt/certs/internal.ca"
      # "key" and "cert" are also valid options here

  - match:
      protocol: "https"

    ssl:
      verify: false # allows any certificate to be used, even self-signed certs

  # since this rule has no "match" section it matches everything
  - timeout: 180000 # 3 minutes
« Settings Securing Console »