Kibana 8.18.0
editKibana 8.18.0
editReview the following information about the Kibana 8.18.0 release.
Known issues
editPDF 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.
Errors in rule executions occur when maintenance windows have filters.
Details
Errors occur when rules run during an active maintenance window that has filters and a matching rule category.
Workaround
Remove any filters added to the active maintenance window.
Resolved
This issue is resolved in 8.18.3.
Observability AI assistant gets stuck in a loop when attempting to call the execute_connector
function.
Details
The Observability AI assistant gets stuck in a loop when calling the execute_connector
function. Instead of completing queries, it times out with the error message Failed to parse function call arguments when converting messages for inference: SyntaxError: Unexpected non-whitespace character after JSON at position 72 and Error: Tool call arguments for execute_connector (...) were invalid
.
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:
Observability AI Assistant - Elastic Managed LLM may be automatically selected as default connector
Details
The Elastic Managed LLM may be automatically selected as your default connector because of existing connector selection logic.
This can occur if you had not previously specified a connector for any of the following reasons:
- You only had one connector available and it was always automatically picked for your conversations.
- You had multiple connectors available but didn’t make a specific selection and used the automatically picked connector for your conversations.
- You previously selected a connector but cleared your browser’s local storage or switched browsers or devices.
And:
- All of your existing connector names come after the “Elastic Managed LLM connector" when sorted alphabetically.
For more information, check #2088
Upgrade Assistant - Rollup jobs need to be stopped before rollup indices are reindexed.
Details
Rollup indices, like all indices, created in 7.x or earlier need to be reindexed in preparation for migration to 9.0. However, in addition to the normal reindex process the rollup job also needs to be accounted for. It needs to be stopped before reindexing begins otherwise there may be a gap in rollup data. The job can be restarted when reindexing is complete.
This needs to be performed manually until addressed in the upgrade assistant code.
For more information, refer to #211850.
Breaking changes
editBreaking changes can prevent your application from optimal operation and performance. Before you upgrade to 8.18.0, review the breaking changes, then mitigate the impact to your application.
Added sub-feature privileges for managing Synthetics private locations.
Details
Permissions to manage private locations in the Synthetics app can now be granted with sub-feature privileges using the API or Kibana’s role management UI. For more information, refer to (#201100).
Deprecations
editThe following functionality is deprecated in 8.18.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.18.0.
Deprecated all security v1 endpoints.
Details
All v1
Kibana security HTTP endpoints have been removed.
-
GET /api/security/v1/logout
has been replaced byGET /api/security/logout
-
GET /api/security/v1/oidc/implicit
has been replaced byGET /api/security/oidc/implicit
-
GET /api/security/v1/oidc
has been replaced by GET/api/security/oidc/callback
-
POST /api/security/v1/oidc
has been replaced by POST/api/security/oidc/initiate_login
-
POST /api/security/v1/saml
has been replaced by POST/api/security/saml/callback
-
GET /api/security/v1/me
has been removed with no replacement.
For more information, refer to #199656.
Impact
Any HTTP API calls to the v1
Kibana security endpoints will fail with a 404 status code starting from version 9.0.0.
Third party OIDC and SAML identity providers configured with v1
endpoints will no longer work.
Action
Update any OIDC and SAML identity providers to reference the corresponding replacement endpoint listed above.
Remove references to the /api/security/v1/me
endpoint from any automations, applications, tooling, and scripts.
Deprecated Logs UI configuration settings.
Details
Legacy and unused configuration settings were deprecated for the Logs UI. For more information, refer to (#201625).
Features
editKibana 8.18.0 adds the following new and notable features.
- Dashboards & Visualizations
- Data ingestion and Fleet
- ES|QL editor
-
-
Adds support for
LOOKUP JOIN
commands (#205762).
-
Adds support for
- Discover
- Elastic Observability solution
-
- Adds the ability to handle multiple prompts for the Rule connector (#209221).
- Adds chat history details to conversation list (#207426).
- Adds createdBy and updatedBy fields to summary documents (#205784).
- Adds space aware private locations (#202634).
- Adds syncField, syncDelay and frequency settings to the API and SLO UI to allow fine-tuning SLO settings directly from the UI. (#200822).
- Elastic Security solution
- For the Elastic Security 8.18.0 release information, refer to Elastic Security Solution Release Notes.
- Kibana security
-
- The Automatic Import functionality is now generally available (#208523).
- Machine Learning
For more information about the features introduced in 8.18.0, refer to What’s new in 8.18.