IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Kibana 8.17.1

edit

The 8.17.1 release includes the following known issues, enhancements, and bug fixes.

Known issues

edit
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.

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

  1. Pause the Kibana instance if possible. If not possible, skip this step.
  2. 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": "*" } }
          ]
        }
      }
    }
  3. 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.

Enhancements

edit
Management
  • Supports wildcards for transforms in the alerting rule flyout (#204226).

Bug fixes

edit
Discover
  • Fixes a bug with adding comments in multiple lines (#203966).
Elastic Observability solution
  • Uses architecture-specific ELSER models (#205851).
  • Stringifies ignored values before rendering (#203312).
  • Fixes an issue with the ViewInAppUrl Custom Threshold Rule routing to the default space instead of the space where it was created (#201793).
Elastic Search solution
  • Align native box connector configs (#203241).
Kibana platform
  • Fixes an issue with short URLs not working for dashboards (#197484).