From 88524a9c20ae8df9b24ae9dcc74471551975e171 Mon Sep 17 00:00:00 2001 From: Joe Reuter Date: Wed, 13 Nov 2024 22:43:18 +0100 Subject: [PATCH] Kibana known issues of 8.16.0 (#200088) Fresh version of https://github.com/elastic/kibana/pull/199995 Known issues of 8.16.0 - https://github.com/elastic/kibana/issues/199902 - https://github.com/elastic/kibana/issues/199892 - https://github.com/elastic/kibana/issues/199891 FYI @paulb-elastic, @consulthys, @vinaychandrasekhar Paul suggested to involve @lcawl & @colleenmcginnis I would invite the owners of those issues to expand/edit the proposed text and add workarounds if any --------- Co-authored-by: Luca Belluccini (cherry picked from commit 20e023b50010b2fa09bf12004effb8d98ef673c6) --- docs/CHANGELOG.asciidoc | 42 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/docs/CHANGELOG.asciidoc b/docs/CHANGELOG.asciidoc index 1d5cd13494b05..cdb06e827db69 100644 --- a/docs/CHANGELOG.asciidoc +++ b/docs/CHANGELOG.asciidoc @@ -85,6 +85,48 @@ include::upgrade-notes.asciidoc[] For information about the {kib} 8.16.0 release, review the following information. +The 8.16.0 release includes the following known issues. + +[float] +[[known-issues-8.16.0]] +=== Known issues + +[discrete] +[[known-199902]] +.Stack Monitoring shows "Unable to load page error" +[%collapsible] +==== +*Details* + +The Stack Monitoring pages Overview, Nodes, Logs can stop working with the error "Unable to load page error". The Stack trace mentions `TypeError: Cannot read properties of undefined (reading 'logsLocator')`. + +*Workaround* + +Disabling the `Set feature visibility > Logs` feature at Kibana Space settings level will prevent the error to occur. Please note the `Logs` feature will not be available on such space. + +It's also possible to `Observability > Logs` feature privilege to `None` on the role level - this will hide the `Logs` feature for individual users and prevent the error for these users as well. + +For more information, refer to {kibana-issue}199902[#199902]. +==== + +[discrete] +[[known-199891-199892]] +.Onboarding, tutorial of APM and OpenTelemetry and some "Beats Only" integrations will show the error "Unable to load page error" +[%collapsible] +==== +*Details* + +Tutorials linked from the {kib} home page show an error "Unable to load page error". The Stack trace mentions `The above error occurred in tutorial_TutorialUi`. + +*Workaround* + +The APM / OpenTelemetry tutorials represented a shortcut to get important parameters to use in the configuration files quickly. +It is still possible to obtain the same parameters following the documentation tutorials of APM. + +More information can be found in the {observability-guide}/apm-collect-application-data.html[APM documentation] and the {observability-guide}/get-started-with-fleet-apm-server.html[Fleet documentation]. + +For information about how to create APM API keys, please check the {observability-guide}/apm-api-key.html#apm-create-an-api-key[API key documentation]. + + +For more information, refer to {kibana-issue}199891[#199891] and {kibana-issue}199892[#199892]. +==== + [float] [[deprecations-8.16.0]] === Deprecations