[Known Issue] Error on Alert Page when upgrading to 8.16.0 (#6169)

* First draft

* Update 8.16.asciidoc

* removed 0

* Mike's suggestions

* Style edits

* bolds page name

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>

---------

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
(cherry picked from commit 222cecb)

Author: 2 people

docs/release-notes/8.16.asciidoc

@@ -56,6 +56,28 @@ On November 12, 2024, it was discovered that manually running a custom query rul
 ====
 // end::known-issue[]
 
+// tag::known-issue-53[]
+[discrete]
+.Alerts page crashes if you upgrade to 8.16 and access it in a non-default {kib} space  
+[%collapsible]
+====
+*Details* +
+On November 14, 2024, it was discovered that the **Alerts** page would crash and display an `Unable to load` error if you upgraded to 8.16 and accessed the page in a non-default {kib} space.
+
+*Workaround* +
+Manually edit your browser's local storage and refresh the **Alerts** page:
+
+NOTE: These instructions only apply to the Google Chrome browser. Modify the steps based on the browser you're using.
+
+. Right-click anywhere on the **Alerts** page, then select *Inspect* to open Chrome's Developer Tools.
+. Go to *Application -> Storage*, then expand *Local Storage*. 
+. Click on the name of your Kibana instance, for example, http://localhost:1234. 
+. Search for the `siem.<space_name>.pageFilters` key, right-click on the value, then click *Delete*. If you have multiple non-default spaces, do this for each space.
+. Refresh the **Alerts** page to reload it.
+
+====
+// end::known-issue-53[]
+
 [discrete]
 [[breaking-changes-8.16.0]]
 ==== Breaking changes