Skip to content
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.

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

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

Merged
merged 8 commits into from
Nov 14, 2024

Conversation

nastasha-solomon
Copy link
Contributor

@nastasha-solomon nastasha-solomon commented Nov 14, 2024

@nastasha-solomon nastasha-solomon self-assigned this Nov 14, 2024
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

Copy link
Contributor

mergify bot commented Nov 14, 2024

This pull request does not have a backport label. Could you fix it @nastasha-solomon? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • v7.x is the label to automatically backport to the 7.x branch.
  • v7./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@nastasha-solomon nastasha-solomon added v8.16.0 v8.17.0 release-notes known-issue Priority: High Issues that are time-sensitive and/or are of high customer importance Effort: Small Issues that can be resolved quickly Team: Threat Hunting Formerly Data Visibility and removed backport-skip labels Nov 14, 2024
@nastasha-solomon nastasha-solomon marked this pull request as ready for review November 14, 2024 16:40
@nastasha-solomon nastasha-solomon requested a review from a team as a code owner November 14, 2024 16:40
logeekal
logeekal previously approved these changes Nov 14, 2024
Copy link
Contributor

@logeekal logeekal left a comment

Choose a reason for hiding this comment

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

Thank you @stash for such a quick turnaround.


. 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.

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

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.)?

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

michaelolo24
michaelolo24 previously approved these changes Nov 14, 2024
Copy link

@michaelolo24 michaelolo24 left a comment

Choose a reason for hiding this comment

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

Looks great, just had one more nit, but not necessary. Thank you for doing this so quickly!

Copy link
Contributor

@benironside benironside left a comment

Choose a reason for hiding this comment

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

Great work putting this together quickly, @nastasha-solomon! Left a couple minor edits

docs/release-notes/8.16.asciidoc Outdated Show resolved Hide resolved
docs/release-notes/8.16.asciidoc Outdated Show resolved Hide resolved
nastasha-solomon and others added 2 commits November 14, 2024 12:52
Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
@nastasha-solomon nastasha-solomon merged commit 222cecb into main Nov 14, 2024
3 checks passed
mergify bot pushed a commit that referenced this pull request Nov 14, 2024
* 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 <91905639+benironside@users.noreply.github.com>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>

---------

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
(cherry picked from commit 222cecb)
mergify bot pushed a commit that referenced this pull request Nov 14, 2024
* 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 <91905639+benironside@users.noreply.github.com>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>

---------

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
(cherry picked from commit 222cecb)
nastasha-solomon added a commit that referenced this pull request Nov 14, 2024
…ckport #6169) (#6172)

* 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 <91905639+benironside@users.noreply.github.com>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>

---------

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
(cherry picked from commit 222cecb)

Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
nastasha-solomon added a commit that referenced this pull request Nov 14, 2024
…kport #6169) (#6171)

* 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 <91905639+benironside@users.noreply.github.com>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>

---------

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
(cherry picked from commit 222cecb)

Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
@nastasha-solomon nastasha-solomon deleted the issue-53-8.16-ki-alerts branch November 18, 2024 15:28
acorretti pushed a commit that referenced this pull request Nov 19, 2024
…ckport #6169) (#6172)

* 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 <91905639+benironside@users.noreply.github.com>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>

---------

Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
(cherry picked from commit 0907421)

Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Effort: Small Issues that can be resolved quickly known-issue Priority: High Issues that are time-sensitive and/or are of high customer importance release-notes Team: Threat Hunting Formerly Data Visibility v8.16.0 v8.17.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants