Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Nov 14, 2024
Merged

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

Changes from 6 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
5b420e7
First draft
nastasha-solomon Nov 14, 2024
d72c606
Update 8.16.asciidoc
nastasha-solomon Nov 14, 2024
13231c9
removed 0
nastasha-solomon Nov 14, 2024
5394c8d
Mike's suggestions
nastasha-solomon Nov 14, 2024
3e5e66a
Style edits
nastasha-solomon Nov 14, 2024
7ad51d9
bolds page name
nastasha-solomon Nov 14, 2024
371a03f
Update docs/release-notes/8.16.asciidoc
nastasha-solomon Nov 14, 2024
48534f9
Update docs/release-notes/8.16.asciidoc
nastasha-solomon Nov 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/release-notes/8.16.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 of 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.
Copy link

@michaelolo24 michaelolo24 Nov 14, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One more quick nit, but not necessary...the example could also be http://mykibana.co

Copy link
Contributor Author

@nastasha-solomon nastasha-solomon Nov 14, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@michaelolo24 to clarify, are you suggesting that we update the example to something more realistic (e.g.: Click on the name of your Kibana instance, for example, http://mykibana.co.) or that we add another example (e.g.: Click on the name of your Kibana instance, for example, http://localhost:1234/ or http://mykibana.co.)?

Copy link

@michaelolo24 michaelolo24 Nov 14, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just something more realistic, but if localhost is a common practice, then no worries

. Search for the `siem.<space_name>.pageFilters` key, right-click on the value, then click *Delete*. If you have multiple non-default spaces, you do this for each space.
. Refresh the **Alerts** page to reload it.

====
// end::known-issue-53[]

[discrete]
[[breaking-changes-8.16.0]]
==== Breaking changes
Expand Down