Skip to content
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

Closed
Tracked by #1059
ph opened this issue Apr 22, 2021 · 6 comments · Fixed by #1473
Closed
Tracked by #1059

How to Debug Elastic Agent as Standalone. #581

ph opened this issue Apr 22, 2021 · 6 comments · Fixed by #1473
Assignees
Labels

Comments

@ph
Copy link
Contributor

ph commented Apr 22, 2021

As a user I would like to debug a local install of the Elastic Agent.

Things to look for

  1. 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.go

  2. Inspect the Log of the running elastic agent

  3. Increase the log level of the running elastic agent

@ph
Copy link
Contributor Author

ph commented Apr 22, 2021

@EricDavisX I believe you have a docs we could use to complete this page?

@EricDavisX
Copy link
Contributor

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:
https://www.elastic.co/guide/en/fleet/master/fleet-troubleshooting.html

@EricDavisX
Copy link
Contributor

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.

@amolnater-qasource
Copy link

Hi @EricDavisX
We have reported a ticket to add some port opening steps for secondary agent connectivity with Fleet Server agent at link #743

We are continuously going through Fleet documents and will report tickets if got any issues.

Thanks
QAS

@dedemorton
Copy link
Contributor

dedemorton commented Jun 3, 2021

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).

@dedemorton
Copy link
Contributor

Closed by #1473

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants