Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Prototype running the shipper under agent using the V1 protocol #46

Closed
Tracked by #13 ...
cmacknz opened this issue May 31, 2022 · 2 comments
Closed
Tracked by #13 ...

Prototype running the shipper under agent using the V1 protocol #46

cmacknz opened this issue May 31, 2022 · 2 comments
Assignees
Labels
Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team v8.4.0

Comments

@cmacknz
Copy link
Member

cmacknz commented May 31, 2022

The agent V2 protocol is what the final version of the shipper should use, but given that it is still under development we should attempt to integrate with the agent as it exists today with the V1 protocol. The V1 version of the protocol is defined in the same proto file as V2: https://github.com/elastic/elastic-agent-client/blob/main/elastic-agent-client.proto

For reference the beats V1 client implementation can be found in the x-pack/libbeat directory: https://github.com/elastic/beats/tree/main/x-pack/libbeat/management

To allow the agent to run the shipper binary, we must define a spec file for it defining how to start the process and how to transform the agent policy into a format the shipper can understand. See the one for metricbeat as an example: https://github.com/elastic/elastic-agent/blob/main/internal/spec/metricbeat.yml

The shipper should be provided the monitoring and output sections of a policy verbatim.

@fearful-symmetry
Copy link
Contributor

PR here for the initial agent-side changes: elastic/elastic-agent#561

@fearful-symmetry
Copy link
Contributor

shipper-side code here: #59

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team v8.4.0
Projects
None yet
Development

No branches or pull requests

2 participants