From 6b2ebb4a4fa73ef17de114c392738c1a9c1dcc69 Mon Sep 17 00:00:00 2001
From: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Date: Thu, 14 Nov 2024 09:11:19 +1100
Subject: [PATCH] [8.x] Kibana known issues of 8.16.0  (#200088) (#200101)

# Backport

This will backport the following commits from `main` to `8.x`:
- [Kibana known issues of 8.16.0
(#200088)](https://github.com/elastic/kibana/pull/200088)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Joe
Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-11-13T21:43:18Z","message":"Kibana
known issues of 8.16.0 (#200088)\n\nFresh version of
https://github.com/elastic/kibana/pull/199995\r\n\r\nKnown issues of
8.16.0\r\n\r\n- https://github.com/elastic/kibana/issues/199902\r\n-
https://github.com/elastic/kibana/issues/199892\r\n-
https://github.com/elastic/kibana/issues/199891\r\n\r\nFYI
@paulb-elastic, @consulthys, @vinaychandrasekhar \r\n\r\nPaul suggested
to involve @lcawl & @colleenmcginnis \r\n\r\nI would invite the owners
of those issues to expand/edit the proposed\r\ntext and add workarounds
if any\r\n\r\n---------\r\n\r\nCo-authored-by: Luca Belluccini
<luca.belluccini@elastic.co>","sha":"20e023b50010b2fa09bf12004effb8d98ef673c6","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v8.16.0","v8.17.0"],"title":"Kibana
known issues of 8.16.0
","number":200088,"url":"https://github.com/elastic/kibana/pull/200088","mergeCommit":{"message":"Kibana
known issues of 8.16.0 (#200088)\n\nFresh version of
https://github.com/elastic/kibana/pull/199995\r\n\r\nKnown issues of
8.16.0\r\n\r\n- https://github.com/elastic/kibana/issues/199902\r\n-
https://github.com/elastic/kibana/issues/199892\r\n-
https://github.com/elastic/kibana/issues/199891\r\n\r\nFYI
@paulb-elastic, @consulthys, @vinaychandrasekhar \r\n\r\nPaul suggested
to involve @lcawl & @colleenmcginnis \r\n\r\nI would invite the owners
of those issues to expand/edit the proposed\r\ntext and add workarounds
if any\r\n\r\n---------\r\n\r\nCo-authored-by: Luca Belluccini
<luca.belluccini@elastic.co>","sha":"20e023b50010b2fa09bf12004effb8d98ef673c6"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200088","number":200088,"mergeCommit":{"message":"Kibana
known issues of 8.16.0 (#200088)\n\nFresh version of
https://github.com/elastic/kibana/pull/199995\r\n\r\nKnown issues of
8.16.0\r\n\r\n- https://github.com/elastic/kibana/issues/199902\r\n-
https://github.com/elastic/kibana/issues/199892\r\n-
https://github.com/elastic/kibana/issues/199891\r\n\r\nFYI
@paulb-elastic, @consulthys, @vinaychandrasekhar \r\n\r\nPaul suggested
to involve @lcawl & @colleenmcginnis \r\n\r\nI would invite the owners
of those issues to expand/edit the proposed\r\ntext and add workarounds
if any\r\n\r\n---------\r\n\r\nCo-authored-by: Luca Belluccini
<luca.belluccini@elastic.co>","sha":"20e023b50010b2fa09bf12004effb8d98ef673c6"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Joe Reuter <johannes.reuter@elastic.co>
---
 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