-
Notifications
You must be signed in to change notification settings - Fork 195
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
[8.17] Existing logsdb impact note needs clarification to avoid confusion #6525
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. |
Looking good @nastasha-solomon I added a final tweak in the issue, just have just missed you making this change. Can you pleaes take a look and address? Thanks! |
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.
LGTM, thank you.
…d confusion (backport #6525) (#6533) * First draft * Mike's edits * lowercasing logsdb (cherry picked from commit 5e89f9c) Co-authored-by: Nastasha Solomon <[email protected]>
…d confusion (backport #6525) (#6532) * First draft * Mike's edits * lowercasing logsdb (cherry picked from commit 5e89f9c) Co-authored-by: Nastasha Solomon <[email protected]>
Partially addresses #6518 by updating the ESS dcos
Preview: Using logsdb index mode with Elastic Security