-
Notifications
You must be signed in to change notification settings - Fork 206
[DOCS] "Unhealthy" Agent status and integration policy errors #2317
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
Conversation
|
@elasticmachine run elasticsearch-ci/docs |
Create troubleshooting topic Add links to troubleshooting Update screenshot General revisions and cleanup
nastasha-solomon
left a comment
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!
| .Disabled to avoid potential system deadlock (Linux) | ||
| [%collapsible] | ||
| ==== | ||
| This section is a placeholder for future documentation. |
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 remember discussing this last week, but still flagging this section anyways in case you wanted to remove it. If this is intentional, disregard this comment.
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.
Yep, we have to have a section for this to avoid breaking other things, and content will be added soon. Leaving the placeholder instead of a blank section, which might look like an error.
benironside
left a comment
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, left a couple suggestions
Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
|
Hi @joepeeples, We have validated the docs attached in this PR and found the below issues under different doc links. Please find below the details:
We will validate this PR once again once the issues mentioned above are fixed. Thank you! |
This comment was marked as resolved.
This comment was marked as resolved.
|
Hi @joepeeples, Thank you for looking into the issues reported. The docs are only missing information about the Linux deadlock troubleshooting. Apart from that, everything looks good. Thank you! |
kevinlog
left a comment
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!
* Update instructions per workflow changes * Add troubleshooting stub * Update Endpoints page, link to t'shooting * Move screenshot * Minor edit * Revsions and new content Create troubleshooting topic Add links to troubleshooting Update screenshot General revisions and cleanup * Small edits, redo screenshot * Reorder troubleshooting sections * moar edits * Apply suggestions from review 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 f01871f)
…#2376) * Update instructions per workflow changes * Add troubleshooting stub * Update Endpoints page, link to t'shooting * Move screenshot * Minor edit * Revsions and new content Create troubleshooting topic Add links to troubleshooting Update screenshot General revisions and cleanup * Small edits, redo screenshot * Reorder troubleshooting sections * moar edits * Apply suggestions from review 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 f01871f) Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
Resolves #2250.
Previews: