We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Meta issue to publicly track Elastic Agent V2 progress.
Actual V2 architecture design.
Related repository: https://github.com/elastic/elastic-agent-shipper
Elastic Agent preparation phase:
[Meta] Remove Elastic Agent V1 control protocol elastic-agent-client#32
Phase 1:
Phase 2: Integrate with the security solution:
Phase 3: Migrate remaining beats and agent inputs
Phase 4
The goal is to reduce the number of connections for Filebeat and Metricbeat instances to remote services.
The goal is to move a uniform output strategy.
The following documentation tasks should be accomplished at a minimum:
The text was updated successfully, but these errors were encountered:
Closing this one as v2 architecture has been released in 8.6
Sorry, something went wrong.
cmacknz
No branches or pull requests
Meta issue to publicly track Elastic Agent V2 progress.
Actual V2 architecture design.
Related repository: https://github.com/elastic/elastic-agent-shipper
Goals
Development Plan
Elastic Agent preparation phase:
[Meta] Remove Elastic Agent V1 control protocol elastic-agent-client#32
Phase 1:
Phase 2: Integrate with the security solution:
Phase 3: Migrate remaining beats and agent inputs
Phase 4
Phase 1: Separate the shipper from Filebeat and Metricbeat under Agent. (See elastic/elastic-agent-shipper#3)
The goal is to reduce the number of connections for Filebeat and Metricbeat instances to remote services.
Phase 2: Integrate with Endpoint security & the Security beats.
The goal is to move a uniform output strategy.
Phase 3:
QA / Testing Needs
Documentation
The following documentation tasks should be accomplished at a minimum:
Target
The text was updated successfully, but these errors were encountered: