Kibana breaking changes

edit

This list summarizes the most important breaking changes in Kibana 7.12.1. For the complete list, go to Kibana breaking changes.

Removes geo threshold alert type

Details
Geo containment alerts and the Geo threshold alert type have similar functionality, so the Geo threshold alert type has been removed. For more information, refer to #89632.

Impact
Use Geo containment alerts.

New saved object upgrade migrations algorithm

Details
When you upgrade to 7.12.0, Kibana uses a new algorithm to migrate saved objects to reduce the downtime caused by temporary issues, such as network errors or temporarily overloaded Elasticsearch clusters. With the new algorithm, Kibana now retries the failed migrations without user intervention, which allows the migration to continue after the issues are resolved. For more information, refer to saved object upgrade migrations.

Impact
Before you upgrade to 7.12.0, review the documentation for rolling back to a previous version of Kibana.

Kibana support for CCS

Details
In 7.12.0, Kibana introduces a major incompatibility with cross-cluster search. When one or more remote Elasticsearch clusters use a version prior to 7.12.0, Discover, Maps, Canvas, and Logs are unable to display the cluster data. For information about the cross-cluster search limitations in Kibana, refer to #94965.

Impact
To display the cluster data in Discover, load documents directly from _source.

  1. Open the main menu, then click Stack Management > Advanced Settings.
  2. Go to discover:searchFieldsFromSource, then select On.
Discover now uses the fields parameter

Details
With the new fields parameter, Discover now shows all fields, including runtime fields, multi-mapped fields like .keyword, and alias fields. Reading from _source is still supported through a switch in Advanced Settings.

Impact
Refer to the blog announcing the change to Discover.