Agent diagnostics#5254
Merged
shainaraskas merged 11 commits intoelastic:mainfrom Mar 5, 2026
Merged
Conversation
Contributor
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
stefnestor
commented
Feb 21, 2026
stefnestor
commented
Feb 21, 2026
stefnestor
commented
Feb 21, 2026
stefnestor
commented
Feb 21, 2026
stefnestor
commented
Feb 21, 2026
stefnestor
commented
Feb 21, 2026
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
Contributor
vishaangelova
force-pushed
the
stef_AgentDiag
branch
from
5f87f49 to
6085079
Compare
Member
|
Hey @stefnestor, I renamed the |
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
Member
Author
|
Super thank you, @vishaangelova 🙏 for your feedback and sorry for missing that doc file name fix. Changes accepted. |
vishaangelova
approved these changes
Mar 5, 2026
Member
vishaangelova
left a comment
vishaangelova
left a comment
There was a problem hiding this comment.
Great update! Thanks!:) Just one comment/suggestion left, but otherwise LGTM!!
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
Member
Author
|
Thank you for unresolving that & apologies I think after it gets 40 comments the UI+I start fighting on getting actions to take effect and telling which failed to so sorry for marking that wrong pre-emptively. |
florent-leborgne
approved these changes
Mar 5, 2026
Member
florent-leborgne
left a comment
florent-leborgne
left a comment
There was a problem hiding this comment.
Experience-docs related changes LGTM
2 tasks
stefnestor
added a commit
that referenced
this pull request
Apr 9, 2026
## Summary 👋 howdy, team! As follow-up to #5254 from Support feedback, adds pulling a [diagnostic for Agentless Integration](https://www.elastic.co/docs/manage-data/ingest/agentless/agentless-integrations-faq#_how_do_i_troubleshoot_an_unhealthy_agent) or "Agentless Elastic Agent" (not quite sure what the official name is suppose to be, just followed existing docs). TIA! 🙏 ## Generative AI disclosure 1. Did you use a generative AI (GenAI) tool to assist in creating this contribution? - [ ] Yes - [X] No --------- Co-authored-by: Visha Angelova <visha.angelova@elastic.co>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
👋 howdy, team! Furthering our standardization of product diagnostic guidance, this ports the existing troubleshooting section into its own page & makes "contact us for Agent" a first-class citizen.
It partially pulls from this top Support article, but mostly just rephrases existing links into one easy-access location.
Generative AI disclosure