-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Beats run under agent should start without reading a configuration file from disk. #31901
Comments
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Switching the assigning to @fearful-symmetry here as they are likely free next, and this will line up more closely with the input V2 work than the shipper work. |
There is a chance this overlaps with the work needed for #31900, ideally they can be done independently but we'll need to sync up first. |
Is this going to be handled purely in APM Server is currently making use of cc @axw |
It should be handled in libbeat, see the change to Essentially instead of reading the configuration from disk it just constructs a default configuration in place with |
For compatibility with the V2 agent control protocol, beats run under agent should start without loading a configuration file from disk. Preferably a beat run under agent should start, establish a V2 control protocol client, and wait for an initial configuration from the agent.
This issue is cloned from @michalpristas's original comment in the V1 protocol removal issue: elastic/elastic-agent-client#32 (comment)
Beats behaviour change
Current
At the moment we handle process as this:
-management.enabled
flagfilebeat.yml
Proposed
-management.enabled
flagmanagement.enabled
flag is not set filebeat loads a config fromfilebeat.yml
otherwise use sane default configurationThe text was updated successfully, but these errors were encountered: