You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a meta issue to track all the items that need to be completed before the Elastic Agent is fully running and working with the new V2 architecture design. This issue tracks both the items that need to be done by the control plane team as well as other teams that interact with the Elastic Agent.
Control Plane
Implement new v2 input specification
Use the v2 input specification to generate the runtime model (aka. what should be running based on policy and v2 input specification)
Refactor component binaries to be pre-extracted inside components directory with v2 specification
Implement the v2 command runtime (runs each sub-process)
Implement the v2 runtime manager (takes the computed runtime model and works to reconcile the model to the actual state)
Implement the v2 server-side for the v2 control protocol
Connect subprocess to Elastic Agent stdout/stderr
Implement coordinator to manage config changes, variables (from composable inputs), and send it to the runtime manager.
Refactor state tracking to use the coordinator as a central location of state management for the Elastic Agent.
Use the new v2 runtime manager for standalone mode
Use the new v2 runtime manager for Fleet mode
Update the inspect command to provide inspection for the v2 runtime
Update Fleet Server to use the new v2 control protocol
Add shipper component runtime model calculation (when shipper enabled by environment) (includes calculating its configuration with processors from connected inputs)
Overview
This is a meta issue to track all the items that need to be completed before the Elastic Agent is fully running and working with the new V2 architecture design. This issue tracks both the items that need to be done by the control plane team as well as other teams that interact with the Elastic Agent.
Control Plane
inspect
command to provide inspection for the v2 runtimeHasStrictExecPerms
for Windows: V2 command work dir #1061 (comment)Known V2 issues
V2: Agent starting multiple instances of filebeat or metricbeat and goes into tight restart loop for the beat process #997
Data Plane
Security
Observability
Shipper Support
Packaging Shipper and Inputs
The text was updated successfully, but these errors were encountered: