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

Integrate Elastic Endpoint's log output and available stats into Elastic Agent 'diagnostic' collection #105

Closed
Tracked by #26930
EricDavisX opened this issue Dec 13, 2021 · 4 comments · Fixed by #242
Assignees
Labels
debugging good first issue Good for newcomers QA:Validated Validated by the QA Team Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v8.3.0

Comments

@EricDavisX
Copy link
Contributor

Describe the enhancement:
would like the Elastic Agent to automatically be able to collect Endpoint logs and any configuration or state that is useful during debugging, when the 'diagnostic' call is made at cli.

Describe a specific use case for the enhancement or feature:
Refer to the Agent's implementation Documentation ticket that started the discussion:
elastic/observability-docs#1284 (comment)

We have confirmed that Beats and OSQuery logs are collected, but that Endpoint is not, when the Agent's 'diagnostic' cli usage is invoked. We can discourse various levels of effort and cost-value proposition here.

  1. Lowest effort / value: on Agent side when invoked Agent can at least note that no Endpoint logs are collected and maybe point to the Endpoint doc's for ref.

  2. higher value / more effort (how much is TBD): Have Agent actually include Endpoint's logs in its collection process. The tools to do this are presumably / believed written, but it would need adjustment on Agent side to take in the log location after getting it sent in automatically (at started up?) or calling out to Endpoint to get it.


This is for the Agent side work, Endpoint will have a separate ticket logged to track, and I'll like back.
This was discussed in email/slack first and I'm transferring it here for tracking.

@EricDavisX EricDavisX added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Dec 13, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@jlind23
Copy link
Contributor

jlind23 commented Jan 13, 2022

@AndersonQ @lykkin can one of you take this one as soon as the 8.2 start?

@AndersonQ
Copy link
Member

I could take it :)

@amolnater-qasource
Copy link

Hi Team
We have revalidated this issue on 8.3.1 BC1 Kibana cloud-staging environment and found it fixed now.

  • sudo elastic-agent diagnostics collect now collects elastic agent and endpoint security logs.

Screenshot:
13

Logs:
elastic-agent-diagnostics-2022-06-30T09-06-31Z-00.zip

Build details:
BUILD: 53549
COMMIT: a4f8dc60edb19553f16c166ea79c83c16572897a

Hence marking this as QA:Validated.
Thanks

@amolnater-qasource amolnater-qasource added the QA:Validated Validated by the QA Team label Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debugging good first issue Good for newcomers QA:Validated Validated by the QA Team Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v8.3.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants