Upgrade Kibana
editUpgrade Kibana
editKibana automatically runs saved object migrations when required. To roll back to an
earlier version in case of an upgrade failure, you must have a
backup snapshot that includes the kibana feature
state. Snapshots include this feature state by default.
For more information, check Migrate saved objects.
Before you start, take the upgrade preparation steps. To upgrade Kibana:
- Shut down all Kibana instances. Kibana does not support rolling upgrades. Upgrading while older Kibana instances are running can cause data loss or upgrade failures.
-
To install the
deborrpmpackage:-
Use
rpmordpkg. This installs all files in their proper locations and will not overwrite the config files. -
Upgrade any plugins by removing the existing plugin and reinstalling the
appropriate version using the
kibana-pluginscript. For more information, see Kibana plugins.
-
Use
-
To install from a
ziportar.gzarchive:-
Extract the archive to a new directory to be sure that you
don’t overwrite the
configordatadirectories. -
Copy the files from the
configdirectory from your old installation to your new installation. -
Copy the files from the
datadirectory from your old installation to your new installation.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.
-
Install the appropriate versions of all your plugins for your new
installation using the
kibana-pluginscript. For more information, see Kibana plugins.
-
Extract the archive to a new directory to be sure that you
don’t overwrite the
- Start Kibana.
Kibana has a new logging system in 8.0 and the log formats have changed. For additional information, see Logging configuration changes.