-
Notifications
You must be signed in to change notification settings - Fork 179
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
Revises 8.x-8.x upgrade guide #5830
base: main
Are you sure you want to change the base?
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few optional suggestions, so went ahead and approved in case you want to merge now. Ping again if you need re-approval!
|
||
Take these extra steps to ensure you are ready for migration. | ||
Follow this guide to upgrade from an 8.x to an 8.x version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Upgrade from 8.x to 8.x" sounds redundant even though I know it's not really. At the risk of over-explaining:
Follow this guide to upgrade from an 8.x to an 8.x version. | |
Follow this guide to upgrade from an earlier 8.x version to a later 8.x version. |
... Ensure that the index and search rate are close to what they were before upgrading. Go to **Stack Monitoring** -> **{es}** -> **Overview**. | ||
+ | ||
TIP: You can also check the index document count using the {ref}/cat-indices.html[cat index API]. | ||
... Verify that SLM is taking snapshots by {ref}/snapshots-take-snapshot.html#check-slm-history[checking the SLM history]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know we already established what SLM means earlier in the page, but it's a different section and this page is pretty dense. Wouldn't hurt to spell it out again.
|
||
. Upgrade your ingest components (such as {ls}, {fleet} and {agent}, {beats}, etc.). For details, refer to the {stack-ref}/upgrading-elastic-stack.html[Elastic Stack upgrade docs]. | ||
|
||
. Validate that Ingest is operating correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
. Validate that Ingest is operating correctly. | |
. Validate that ingest is operating correctly. |
.. Open *Discover*, go through data views for each of your expected ingest data streams, and ensure that data is being ingested in the expected format and volume. | ||
|
||
. Validate that {elastic-sec} is operating correctly. | ||
.. Re-enable your desired SIEM detection rules (rule management), and ensure that enabled rules are running without errors or warnings (rule monitoring). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like these might be references to specific UI tabs on the Rules page, so capitalize:
.. Re-enable your desired SIEM detection rules (rule management), and ensure that enabled rules are running without errors or warnings (rule monitoring). | |
.. Re-enable your desired SIEM detection rules (Rule Management), and ensure that enabled rules are running without errors or warnings (Rule Monitoring). |
Or maybe even more clarity:
.. Re-enable your desired SIEM detection rules (rule management), and ensure that enabled rules are running without errors or warnings (rule monitoring). | |
.. On the Rules page, re-enable your desired SIEM detection rules (Rule Management tab), and ensure that enabled rules are running without errors or warnings (Rule Monitoring tab). |
Contributes to #5302.
Revises the instructions for upgrading from an 8.x to an 8.x version. Mostly reuses the content from the 7.17 to 8.x upgrade guide, but without the 7.17-specific information.