-
Notifications
You must be signed in to change notification settings - Fork 166
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
How to Debug Elastic Agent as Standalone. #581
Comments
@EricDavisX I believe you have a docs we could use to complete this page? |
I'm still working on refining the personal document with tips and tricks. I'll focus on that shortly. I expect we'll want to update this page with it: |
the team has put some additions into the document. @ph when you're free, if you want to review and advise on more specifics we should add (it is hard to know how far to go in the 'troubleshooting guide' versus just regular doc for intended use. @amolnater-qasource @dikshachauhan-qasource if you can review the above page specifically, and think about what we've learned recently and what we might want to highlight for troubleshooting (specifically) for a stand-alone Agent I would appreciate the feedback here! Thank you. |
Hi @EricDavisX We are continuously going through Fleet documents and will report tickets if got any issues. Thanks |
We also need to document what each status means (for the values returned by the status command and the statuses that are displayed in the UI). |
Closed by #1473 |
As a user I would like to debug a local install of the Elastic Agent.
Things to look for
Retrieve the status of the running elastic agent using the status subcommand.
elastic-agent status
https://github.com/elastic/beats/blob/master/x-pack/elastic-agent/pkg/agent/cmd/status.goInspect the Log of the running elastic agent
Increase the log level of the running elastic agent
The text was updated successfully, but these errors were encountered: