-
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
[Elastic Agent] Add ability to communicate and control the running agent daemon. #20142
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
@ph @ruflin @michalpristas Implementing this will greatly help with UX, re-exec testing, and upgrade testing. Let me know what you think. |
Another improvement this brings is also the installation process. Currently we install Agent without starting the service and the configuration is basic and trying to write system metrics to I believe with the above changes we should do the following:
|
@blakerouse I really like this plan, the description is top! I like the proposal for the empty configuration and the reload, we had an issue to allow have a enroll and run from a same subcommand. But I think what you are suggesting for service is even better than that and will simplify the workflow. @EricDavisX The above will impact testings for the best, you might have suggestion too? |
sounds good to me. |
@blakerouse Can this be closed? |
@ph I was leaving it open until |
how much, if any, coordination do we need to do now to ensure design is compatible with Endpoint, @blakerouse ? @ferullo fyi.
|
@EricDavisX Endpoint should just work, once Agent is upgraded it will then upgrade Endpoint to match the same version of Agent. |
To provide a rich UX for the Elastic Agent we need to provide a way to communicate and control the running Elastic Agent.
Information that needs to be able to be retrieved from the local agent:
Below documents the commands and expected outputs:
version
Same version
Not running
Different versions running
status
restart
The different
[/]
below are showing interactive progress of what the command will report as its performing the restart action. It will then just printSuccessfully restarted
over the progress.upgrade
The different
[/]
below are showing interactive progress of what the command will report as its performing the restart action. It will then just printSuccessfully restarted
over the progress.Next-version in same major
Next major
Specific version
The text was updated successfully, but these errors were encountered: