Use Kibana in a production environment

How you deploy Kibana largely depends on your use case. If you are the only user, you can run Kibana on your local machine and configure it to point to whatever Elasticsearch instance you want to interact with. Conversely, if you have a large number of heavy Kibana users, you might need to load balance across multiple Kibana instances that are all connected to the same Elasticsearch instance.

While Kibana isn’t terribly resource intensive, we still recommend running Kibana separate from your Elasticsearch data or master nodes. To distribute Kibana traffic across the nodes in your Elasticsearch cluster, you can run Kibana and an Elasticsearch client node on the same machine. For more information, see Load balancing across multiple Elasticsearch nodes.

Use Elastic Stack security features

You can use Elastic Stack security features to control what Elasticsearch data users can access through Kibana.

When security features are enabled, Kibana users have to log in. They need to have a role granting Kibana privileges as well as access to the indices they will be working with in Kibana.

If a user loads a Kibana dashboard that accesses data in an index that they are not authorized to view, they get an error that indicates the index does not exist.

For more information on granting access to Kibana, see Granting access to Kibana.

Require Content Security Policy

Kibana uses a Content Security Policy to help prevent the browser from allowing unsafe scripting, but older browsers will silently ignore this policy. If your organization does not need to support Internet Explorer 11 or much older versions of our other supported browsers, we recommend that you enable Kibana’s strict mode for content security policy, which will block access to Kibana for any browser that does not enforce even a rudimentary set of CSP protections.

To do this, set csp.strict to true in your kibana.yml:

  1. csp.strict: true

Enable SSL

See Encrypt communications.

Load Balancing across multiple Elasticsearch nodes

If you have multiple nodes in your Elasticsearch cluster, the easiest way to distribute Kibana requests across the nodes is to run an Elasticsearch Coordinating only node on the same machine as Kibana. Elasticsearch Coordinating only nodes are essentially smart load balancers that are part of the cluster. They process incoming HTTP requests, redirect operations to the other nodes in the cluster as needed, and gather and return the results. For more information, see Node in the Elasticsearch reference.

To use a local client node to load balance Kibana requests:

  1. Install Elasticsearch on the same machine as Kibana.

  2. Configure the node as a Coordinating only node. In elasticsearch.yml, set node.data, node.master and node.ingest to false:

    1. # 3. You want this node to be neither master nor data node nor ingest node, but
    2. #    to act as a "search load balancer" (fetching data from nodes,
    3. #    aggregating results, etc.)
    4. #
    5. node.master: false
    6. node.data: false
    7. node.ingest: false

  3. Configure the client node to join your Elasticsearch cluster. In elasticsearch.yml, set the cluster.name to the name of your cluster.

    1. cluster.name: "my_cluster"

  4. Check your transport and HTTP host configs in elasticsearch.yml under network.host and transport.host. The transport.host needs to be on the network reachable to the cluster members, the network.host is the network for the HTTP connection for Kibana (localhost:9200 by default).

    1. network.host: localhost
    2. http.port: 9200
    4. # by default transport.host refers to network.host
    5. transport.host: <external ip>
    6. transport.tcp.port: 9300 - 9400

  5. Make sure Kibana is configured to point to your local client node. In kibana.yml, the elasticsearch.hosts setting should be set to ["localhost:9200"].

    1. # The Elasticsearch instance to use for all your queries.
    2. elasticsearch.hosts: ["http://localhost:9200"]

Load balancing across multiple Kibana instances

To serve multiple Kibana installations behind a load balancer, you must change the configuration. See Configuring Kibana for details on each setting.

Settings unique across each Kibana instance:

  1. server.uuid
  2. server.name

Settings unique across each host (for example, running multiple installations on the same virtual machine):

  1. logging.dest
  2. path.data
  3. pid.file
  4. server.port

Settings that must be the same:

  1. xpack.security.encryptionKey //decrypting session cookies
  2. xpack.reporting.encryptionKey //decrypting reports
  3. xpack.encryptedSavedObjects.encryptionKey // decrypting saved objects

Separate configuration files can be used from the command line by using the -c flag:

  1. bin/kibana -c config/instance1.yml
  2. bin/kibana -c config/instance2.yml

High availability across multiple Elasticsearch nodes

Kibana can be configured to connect to multiple Elasticsearch nodes in the same cluster. In situations where a node becomes unavailable, Kibana will transparently connect to an available node and continue operating. Requests to available hosts will be routed in a round robin fashion.

Currently the Console application is limited to connecting to the first node listed.

In kibana.yml:

  1. elasticsearch.hosts:
  2.   - http://elasticsearch1:9200
  3.   - http://elasticsearch2:9200

Related configurations include elasticsearch.sniffInterval, elasticsearch.sniffOnStart, and elasticsearch.sniffOnConnectionFault. These can be used to automatically update the list of hosts as a cluster is resized. Parameters can be found on the settings page.

Memory

Kibana has a default maximum memory limit of 1.4 GB, and in most cases, we recommend leaving this unconfigured. In some scenarios, such as large reporting jobs, it may make sense to tweak limits to meet more specific requirements.

You can modify this limit by setting --max-old-space-size in the node.options config file that can be found inside kibana/config folder or any other configured with the environment variable KBN_PATH_CONF (for example in debian based system would be /etc/kibana).

The option accepts a limit in MB:

  1. --max-old-space-size=2048

Most Popular