Loading

Kibana known issues

For Elastic Observability known issues, refer to Elastic Observability known issues.

For Elastic Security known issues, refer to Elastic Security known issues.

Reports created in non-default Kibana spaces aren't shown in the Reporting UI

Applies to: Elastic Stack 9.1.0, 9.1.1

Details

After creating a report in a non-default Kibana space, the document exists in the .kibana-reporting index but isn't shown in the Reporting UI.

Issues with rules occur when xpack.alerting.rules.run.alerts.max is set to a value greater than 5000

Applies to: Elastic Stack 9.0.3, 9.0.4, 9.1.0

Resolved

This issue is resolved in Elastic Stack 9.1.0 and 9.1.2.

Details

If you've set xpack.alerting.rules.run.alerts.max to a value greater than 5000, you will encounter Result window is too large error messages when a maintenance window is active.

Action

To mitigate the issue, set xpack.alerting.rules.run.alerts.max to a value equal to or less than 5000.

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

Applies to: Elastic Stack 9.0.0

Details

Starting in 9.0.0, the default value of server.protocol is http2. PDF and PNG reports will fail when this setting is used in this release.

Action

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

Resolved

This issue is resolved in Elastic Stack 9.0.0, 9.0.4, 9.1.0.

Dashboard Copy link doesn't work when sharing from a space other than the default space

Applies to: Elastic Stack 9.0.3

Details

When attempting to share a dashboard from a space that isn't the default space, the Copy link action never completes.

Action

To avoid this error, don't upgrade Kibana to Elastic Stack 9.0.3 or upgrade Kibana to Elastic Stack 9.0.4 when available.

Resolved

This issue is resolved in Elastic Stack 9.0.4.

Upgrading Kibana from 8.18.x to 9.0.2 fails due to a configuration conflict in the kibana.yml file

Applies to: Elastic Stack 9.0.2

Details

Upgrading Kibana from version 8.18.x to 9.0.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 9.0.2.

Action

To temporarily resolve the issue and allow the upgrade to proceed, follow these steps:

  1. Remove the xpack.alerting.cancelAlertsOnRuleTimeout: false setting from the kibana.yml file.
  2. Restart Kibana to apply the changes.

Resolved

This was resolved in Elastic Stack 9.0.3.

Errors in rule executions occur when maintenance windows have filters

Applies to: Elastic Stack 9.0.0, 9.0.1, 9.0.2

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 was resolved in Elastic Stack 9.0.3.