IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Kibana 8.17.1 Enhancements and bug fixes »

› ›

Kibana 8.17.0

edit

A newer version is available. Check out the latest documentation.

Kibana 8.17.0

edit

Coming in 8.17.0.

For information about the Kibana 8.17.0 release, review the following information.

The 8.17.0 release includes the following known issues.

Known issues

edit

Errors appear when loading Observability Infrastructure inventory views after upgrading to version 8.10.0 or higher.

Details
After upgrading to version 8.10.0 or higher, you may encounter errors when loading inventory views.

For more information, refer to #187254.

Workaround
You can mitigate the issue by completing the following steps:

Search the .kibana_* index for type: inventory_view.
Copy the _id field, which will be formatted as inventory-view:<id>. For example, inventory-view:3d3d06b0-f873-4373-8446-f6a8341cd8b1. Omit the inventory-view: portion and copy only the string of _id characters.
The offending documents are those with fields inventory-view.legend.steps > 18. Delete these documents by running the following in Console:

DELETE kbn:/api/infra/inventory-views/<id>

Observability AI assistant Knowledge Base entries with empty text can lead to Kibana OOM or restarts.

Details
The semantic text migration can cause excessive traffic to a cluster and might eventually cause the Kibana instance to crash due to OOM, together with increase of requests to Elasticsearch & ML nodes.

The problem can occur when there is one or more empty text Knowledge Base documents.

The migration script does not handle this scenario and will indefinitely update the same document.

Because the document update involves semantic_text an ML node is kept warm further increasing the costs.

The issue involves semantic_text field type (and thus the semantic_text migration which is causing this issue), introduced in the knowledge base feature in 8.17.

Workaround

Pause the Kibana instance if possible. If not possible, skip this step.

Run a dry run query to identify if you have empty Knowledge Base documents. If you have at least 1 hit, you can be affected by the problem.

GET .kibana-observability-ai-assistant-kb/_search
{
  "query": {
    "bool": {
      "must": [{ "exists": { "field": "text" }}],
      "must_not": [ { "wildcard": { "text": "*" } }
      ]
    }
  }
}

Execute the deletion. For extra safety, you might want to trigger a snapshot before executing it.

POST .kibana-observability-ai-assistant-kb/_delete_by_query
{
  "query": {
    "bool": {
      "must": [{ "exists": { "field": "text" }}],
      "must_not": [ { "wildcard": { "text": "*" } }
      ]
    }
  }
}

For more information, check:

PDF and PNG reports time out and fail with an invalid header error if server.protocol is set to http2

Details
If you’ve changed the server.protocol value to http2, PDF and PNG reports will fail when you export them from the dashboard, visualization, or Canvas workpad that you’re generating a report for.

Workaround
To temporarily resolve the issue, set server.protocol to http1.

Resolved
This issue is resolved in 8.17.9, 8.18.4, 8.19.0 and later.

Upgrade Assistant displays configured source mode in mappings as critical deprecation issue.

Details
When upgrading to a newer version, the Upgrade Assistant displays critical warnings for the deprecation of configuring source mode in mappings. These warnings can safely be ignored.

For more information, refer to #206400.

Deprecations

edit

The following functionality is deprecated in 8.17.0, and will be removed in 9.0.0. Deprecated functionality does not have an immediate impact on your application, but we strongly recommend you make the necessary updates after you upgrade to 8.17.0.

The Observability > Logs > Explorer app is now deprecated in favor of Discover.

Details
Both the Logs Explorer and Logs Stream applications are now deprecated and will be removed in 9.0. We continue to make enhancements to Discover to offer similar functionality in 9.x.

Features

edit

Kibana 8.17.0 adds the following new and notable features.

Cases

Files can now be attached to cases directly via API (#198377).

Data ingestion and Fleet

Exposes advanced file logging configuration in the UI (#200274).

Dashboards and visualizations

AIOps: Adds Log Rate Analysis embeddable for dashboards (#197943).

Discover and ES|QL

Keeps the preferred chart configuration when possible when writing ES|QL queries in Discover (#197453).

ES|QL

Adds the ability to star queries in the ES|QL editor (#198362).

Elastic Observability solution

Adds ability to show monitors from all permitted spaces in a single view in Synthetics (#196109).
Adds fix it flow for field limit (#195561).
Adds permissions to reopen and add comments to cases (#194898).
Adds built-in definitions for core Kubernetes entities (#196916).

Elastic Security solution

For the Elastic Security 8.17.0 release information, refer to Elastic Security Solution Release Notes.

Kibana security

Kibana’s FIPS mode is no longer considered experimental (#200734).
When running in FIPS mode, Kibana now forbids usage of PKCS12 configuration options (#192627).

For more information about the features introduced in 8.17.0, refer to What’s new in 8.17.

« Kibana 8.17.1 Enhancements and bug fixes »