Kibana 8.18.2
editKibana 8.18.2
editThe 8.18.2 release includes the following known issues and fixes.
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 - 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
Upgrading Kibana from 8.x to 8.18.2 fails due to a configuration conflict in the kibana.yml file.
This issue is resolved in version 8.18.3 (#222263).
Details
Upgrading Kibana from version 8.x to 8.18.2 fails due to a configuration conflict if xpack.alerting.cancelAlertsOnRuleTimeout
is set to false
in the kibana.yml
file. Kibana fails to boot and shows a fatal error message in the Kibana logs that’s similar to the following:
FATAL Error: Rule type "transform_health" cannot have both cancelAlertsOnRuleTimeout set to false and autoRecoverAlerts set to true.
This failure occurs when the xpack.alerting.cancelAlertsOnRuleTimeout
setting is set to false
, which is incompatible with the default configuration of an internal setting (autoRecoverAlerts
) in 8.18.2.
Workaround
To temporarily resolve the issue and allow the upgrade to proceed, follow these steps:
-
Remove the
xpack.alerting.cancelAlertsOnRuleTimeout: false
setting from thekibana.yml
file. - Restart Kibana to apply the changes.
Fixes
edit- Dashboards and Visualizations
- Elastic Observability Solution
- Elastic Security solution
- For the Elastic Security 8.18.2 release information, refer to Elastic Security Solution Release Notes.