Kibana 8.19.13
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Kibana 8.19.13
editThe 8.19.13 release includes the following known issues and fixes.
This release contains fixes for potential security vulnerabilities. Check our security advisory for more details.
Known issues
editStack and Observability alerts remain active instead of transitioning to recovered.
Details
Some Stack and Observability alerts send recovery notifications (for example, Slack, email, or webhook) but remain active in Kibana instead of transitioning to recovered.
Workaround
Manually untrack stale alerts or upgrade to 8.19.15, 9.3.4, or 9.4.0.
Resolved
This issue is resolved in 8.19.15, 9.3.4, and 9.4.0.
Fixes
edit- Alerting and cases
-
- Fixes an issue where webhook connector updates failed when the external service returned a 204 (no content) response (#251090).
- Data ingestion and Fleet
-
- Filters out unenrolled agents in the cleanup policy revisions task (#254899).
- Discover
-
- Fixes a rendering issue in the Attributes tab on the trace details flyout that caused the UI to become unresponsive (#255173).
- Elastic Observability solution
-
-
Passes alerts data view to
buildEsQueryfor correct wildcard queries on keyword fields (#255225). -
Fixes a crash in APM apps when invalid values were passed to
rangeFromandrangeToURL query parameters (#256887). - Fixes an error on the SLO burn rate alert details page for suppressed alerts (#256435).
-
Fixes a 500 error and infinite loading on the APM Error group details page when the related transaction document is missing the
transaction.sampledfield (#255788).
-
Passes alerts data view to
- Elastic Security solution
- For the Elastic Security 8.19.13 release information, refer to Elastic Security Solution Release Notes.
- Management
- Search
-
- Fixes focus behavior when there are errors in the connector flyout form (#255770).