IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Upgrade Kibana Upgrade migrations »
Elastic Docs ›Kibana Guide [7.8] ›Set up Kibana ›Upgrade Kibana

Standard upgrade

edit

Standard upgrade

edit

6.7 includes an Upgrade Assistant to help you prepare for your upgrade to 7.0. To access the assistant, go to Management > 7.0 Upgrade Assistant.

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 multiple Kibana instances

edit

Kibana does not support rolling upgrades. If you’re running multiple Kibana instances, all instances should be stopped before upgrading.

Different versions of Kibana running against the same Elasticsearch index, such as during a rolling upgrade, can cause upgrade migration failures and data loss. This is because acknowledged writes from the older instances could be written into the old index while the migration is in progress. To prevent this from happening ensure that all old Kibana instances are shutdown before starting up instances on a newer version.

The first instance that triggers saved object migrations will run the entire process. Any other instances started up while a migration is running will log a message and then wait until saved object migrations has completed before they start serving HTTP traffic.

Upgrade using a deb or rpm package

edit
  1. Stop the existing Kibana process using the appropriate command for your system. If you have multiple Kibana instances connecting to the same Elasticsearch cluster ensure that all instances are stopped before proceeding to the next step to avoid data loss.

  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.

Upgrade 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 monitoring features, 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. If you have multiple Kibana instances connecting to the same Elasticsearch cluster ensure that all instances are stopped before proceeding to the next step to avoid data loss.
  6. Start the new Kibana process.
« Upgrade Kibana Upgrade migrations »