-
Notifications
You must be signed in to change notification settings - Fork 159
Add troubleshooting section for Elastic Agent upgrade failing on Windows #1750
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
Add troubleshooting section for Elastic Agent upgrade failing on Windows #1750
Conversation
🔍 Preview links for changed docs: 🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes. |
be5b938
to
753cac4
Compare
753cac4
to
be5b938
Compare
e8f7496
to
4d80224
Compare
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.
Looks great. Thank you.
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.
Left minor suggestions inline, mostly related to present (not future) tense and "one sentence per line" for easier GitHub review. Otherwise, LGTM! 🦋
Co-authored-by: Karen Metts <[email protected]>
This PR adds a new section in Ingest tools > Fleet and Elastic Agent > Common problems for troubleshooting an Elastic Agent upgrade failure on Windows caused by Windows desktop heap exhaustion.
Closes #1775
🔍 Preview link: troubleshoot/ingest/fleet/common-problems.md