- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 8.0
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Enterprise Search settings
- Fleet settings
- i18n settings
- Logging settings
- Logs settings
- Metrics settings
- Monitoring settings
- Reporting settings
- Search sessions settings
- Secure settings
- Security settings
- Spaces settings
- Task Manager settings
- Telemetry settings
- URL drilldown settings
- Start and stop Kibana
- Access Kibana
- Securing access to Kibana
- Add data
- Upgrade Kibana
- Configure security
- Configure reporting
- Configure logging
- Configure monitoring
- Command line tools
- Production considerations
- Discover
- Dashboard and visualizations
- Canvas
- Maps
- Build a map to compare metrics by country or region
- Track, visualize, and alert on assets in real time
- Map custom regions with reverse geocoding
- Heat map layer
- Tile layer
- Vector layer
- Plot big data
- Search geographic data
- Configure map settings
- Connect to Elastic Maps Service
- Import geospatial data
- Troubleshoot
- Reporting and sharing
- Machine learning
- Graph
- Alerting
- Observability
- APM
- Security
- Dev Tools
- Fleet
- Osquery
- Stack Monitoring
- Stack Management
- REST API
- Get features API
- Kibana spaces APIs
- Kibana role management APIs
- User session management APIs
- Saved objects APIs
- Data views API
- Index patterns APIs
- Alerting APIs
- Action and connector APIs
- Cases APIs
- Import and export dashboard APIs
- Logstash configuration management APIs
- Machine learning APIs
- Short URLs APIs
- Get Task Manager health
- Upgrade assistant APIs
- Kibana plugins
- Accessibility
- Release notes
- Developer guide
Migrate saved objects
editMigrate saved objects
editEach time you upgrade Kibana, an upgrade migration is performed to ensure that all saved objects are compatible with the new version.
To help you prepare for the upgrade to 8.0.0, 7.17.0 includes an Upgrade Assistant. To access the assistant, go to Stack Management > Upgrade Assistant.
Kibana 7.12.0 and later uses a new migration process and index naming scheme. Before you upgrade, read the documentation for your version of Kibana.
The following instructions assumes Kibana is using the default index names. If the kibana.index
or xpack.tasks.index
configuration settings are different from the default, adapt the instructions accordingly.
How saved objects migrations work
editSaved objects are stored in two indices:
-
.kibana_{kibana_version}_001
, e.g. for Kibana 7.12.0.kibana_7.12.0_001
. -
.kibana_task_manager_{kibana_version}_001
, e.g. for Kibana 7.12.0.kibana_task_manager_7.12.0_001
.
The index aliases .kibana
and .kibana_task_manager
always point to
the most up-to-date saved object indices.
When you start a new Kibana installation, an upgrade migration is performed before starting plugins or serving HTTP traffic. Before you upgrade, shut down old nodes to prevent losing acknowledged writes. To reduce the likelihood of old nodes losing acknowledged writes, Kibana 7.12.0 and later adds a write block to the outdated index.
The following tables lists the saved objects indices used by previous Kibana versions.
Table 1. Saved object indices and aliases per Kibana version
Upgrading from version | Outdated index (alias) |
---|---|
6.5.0 through 7.3.x |
|
7.4.0 through 7.11.x |
|
On this page