Note for Elastic Security users added to 7.x to 9.x upgrade doc #4391
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -90,7 +90,16 @@ | |||||
|
|
||||||
| It's highly recommended to start this upgrade from the latest 7.17.x patch release to ensure that you’re using the most recent version of the Elastic Upgrade Assistant. You should also upgrade to the latest available 8.19.x patch release so that the same benefits apply when you later upgrade to 9.x. | ||||||
|
|
||||||
| :::::{note} | ||||||
| If you use the [{{elastic-sec}} solution](/solutions/security.md), read the full [Upgrade {{elastic-sec}} from 7.17 to 8.x](https://www.elastic.co/guide/en/security/8.19/upgrade-7.17-8x.html) guide when planning the upgrade. | ||||||
|
Collaborator
There was a problem hiding this comment. perhaps this should be a
Suggested change
Contributor
There was a problem hiding this comment. I'm in favor of switching the admonition to a warning and using the stronger, more direct language. There's a good amount of pre and post checks that users will need to complete when moving from 7.17->8.x, so the more emphasis, the better. |
||||||
|
|
||||||
| In particular: | ||||||
| * Export all custom detection rules as a backup before upgrading, in case there are issues with the detection engine after the upgrade. | ||||||
|
Contributor
There was a problem hiding this comment. We don't explicitly recommend this in the guide for upgrading from 7.17.x -> 8.x, but there's really no harm in advising it here. If anything, it's sound advice for upgrading to any Security version. |
||||||
| * Review [alert schema changes](https://www.elastic.co/guide/en/security/8.19/alert-schema.html) if alerts are forwarded to an external SOAR, or if you directly query alert data in custom dashboards or tools. | ||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||
| * Plan for the [post-upgrade steps](https://www.elastic.co/guide/en/security/8.19/upgrade-7.17-8x.html#_post_upgrade_steps), such as re-enabling and verifying rules after the upgrade. | ||||||
| ::::: | ||||||
|
|
||||||
| ### 8.19 upgrade preparations | ||||||
|
|
||||||
| The [upgrade preparation steps from 7.x](https://www.elastic.co/guide/en/elastic-stack/8.19/upgrading-elastic-stack.html#prepare-to-upgrade) are designed to prevent upgrade failures by detecting and addressing internal incompatibilities, including deprecated settings that are no longer supported in the next release. | ||||||
|
|
||||||
|
|
||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@natasha-moore-elastic or @jmikell821 can you please take a look at this change.
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.
hah. never mind, @nastasha-solomon beat me to it (again!)
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.
me jumping on PR reviews:
