IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Upgrading Kibana Standard Upgrade with Reindex »
Elastic Docs ›Kibana User Guide [6.3] ›Set Up Kibana ›Upgrading Kibana

Standard Upgrade

edit

Standard Upgrade

edit

A standard upgrade is the most straightforward way to upgrade Kibana, and it’s possible when you’re upgrading from Kibana version 4.2 or higher.

If you haven’t already, consult this table to verify that standard upgrade is supported for your version of Kibana.

If you’ve saved and/or exported objects in Kibana that rely on the Elasticsearch Query DSL, make sure to check the Elasticsearch breaking changes documentation and take the necessary remediation steps as per those instructions.

Upgrading using a deb or rpm package

edit
  1. Stop the existing Kibana process using the appropriate command for your system.

  2. Use rpm or dpkg to install the new package. All files should be placed in their proper locations and config files should not be overwritten.

    Kibana 4.x used a different config location than 5.0+, so if you’re upgrading from 4.x, you will need to copy the configurations from your old config (/opt/kibana/config/kibana.yml) to your new config (/etc/kibana/kibana.yml).

    Make sure you remove or update any configurations that are indicated in the breaking changes documentation otherwise Kibana will fail to start.

  3. Upgrade any plugins by removing the existing plugin and reinstalling the appropriate version using the kibana-plugin script. Check out the plugins documentation for more information.
  4. Start the new Kibana process using the appropriate command for your system.

Upgrading using a zip or tar.gz archive

edit

  1. Extract the zip or tar.gz archive to a new directory to be sure that you don’t overwrite the config or data directories.

    If you use X-Pack monitoring, you must re-use the data directory when you upgrade Kibana. Otherwise, the Kibana instance is assigned a new persistent UUID and becomes a new instance in the monitoring data.

  2. Copy the files from the config directory from your old installation to your new installation. Make sure you remove or update any configurations that are indicated in the breaking changes documentation otherwise Kibana will fail to start.
  3. Copy the files from the data directory from your old installation to your new installation.
  4. Install the appropriate versions of all your plugins for your new installation using the kibana-plugin script. Check out the plugins documentation for more information.
  5. Stop the old Kibana process.
  6. Start the new Kibana process.
« Upgrading Kibana Standard Upgrade with Reindex »