Integrate Elastic Endpoint's log output and available stats into Elastic Agent 'diagnostic' collection #105
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
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.
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.
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.
The text was updated successfully, but these errors were encountered: