IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Using Kibana in a production environment Standard upgrade »
Elastic Docs ›Kibana Guide [7.3] ›Set Up Kibana

Upgrading Kibana

edit

Upgrading Kibana

edit

Depending on the Kibana version you’re upgrading from, the upgrade process to 7.3.2 varies. The following upgrades are supported:

  • Between minor versions
  • From 5.6 to 6.8
  • From 6.8 to 7.3.2
  • From any version since 7.3.0 to 7.3.2

The following table shows the recommended upgrade paths to 7.3.2.

Upgrade from Recommended upgrade path to 7.3.2

A previous 7.3 version (e.g., 7.3.0)

Upgrade to 7.3.2

7.0–7.13

Upgrade to 7.3.2

6.8

Upgrade to 7.3.2

6.0–6.7
  1. Upgrade to 6.8
  2. Upgrade to 7.3.2

5.6
  1. Upgrade to 6.8
  2. Upgrade to 7.3.2

5.0–5.5
  1. Upgrade to 5.6
  2. Upgrade to 6.8
  3. Upgrade to 7.3.2

The upgrade path from 6.8 to 7.0 is not supported.

Before you begin

edit

Kibana automatically runs upgrade migrations when required. To roll back to an earlier version in case of an upgrade failure, you must have a backup snapshot available. Use Snapshot and Restore to back up Kibana data by targeting the .kibana* indices. For more information see upgrade migrations.

Before you upgrade Kibana:

  • Consult the breaking changes.
  • Back up your data with Snapshot and Restore. To roll back to an earlier version, you must have a snapshot of the .kibana* indices.
  • Although not a requirement for rollbacks, we recommend taking a snapshot of all Kibana indices created by the plugins you use such as the .reporting* indices created by the reporting plugin.
  • Before you upgrade production servers, test the upgrades in a dev environment.
  • See preventing migration failures for common reasons upgrades fail and how to prevent these.
  • If you are using custom plugins, check that a compatible version is available.
  • Shut down all Kibana instances. Running more than one Kibana version against the same Elasticseach index is unsupported. Upgrading while older Kibana instances are running can cause data loss or upgrade failures.

To identify the changes you need to make to upgrade, and to enable you to perform an Elasticsearch rolling upgrade with no downtime, you must upgrade to 6.7 before you upgrade to 7.0.

For a comprehensive overview of the upgrade process, refer to Upgrading the Elastic Stack.

Upgrading from 5.x or earlier

edit

Elasticsearch can read indices created in the previous major version. Before you upgrade to 7.0.0, you must reindex or delete any indices created in 5.x or earlier. For more information, refer to Upgrading the Elastic Stack.

When your reindex is complete, follow the Standard upgrade instructions.

Upgrading from 6.x

edit

The recommended path is to upgrade to 6.7 before upgrading to 7.0. This makes it easier to identify the required changes, and enables you to use the Upgrade Assistant to prepare for your upgrade to 7.0.

The ability to import Kibana 6.x saved searches, visualizations, and dashboards is supported.

Upgrading from 6.7

edit

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

After you have addressed any issues that were identified by the Upgrade Assistant, upgrade to 7.0.

Known issues

edit

"shard failed" error when viewing Beats dashboards in Kibana

edit

After upgrading to Elasticsearch 7.0, any indices created by Beats 6.6 or older will not work in Kibana dashboards until the index.query.default_field setting is added to each index. Indices created in Beats 6.7 or later are unaffected. To add the setting to the index, you can use the 7.0 Upgrade Assistant, or add the setting manually .

« Using Kibana in a production environment Standard upgrade »