Stop Elastic Agentedit
This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
This experimental release allows you to try out new capabilities. There is no migration path for future releases. You must test in a dedicated cluster. Delete the cluster when you are done. You will not be able to upgrade the cluster.
To stop Elastic Agent and its related executables, stop the Elastic Agent process. Use the commands that work for your system.
Windows:
If you installed the Agent as a service, stop the service. If necessary, use Task Manager on Windows to stop Elastic Agent. This will kill the Elastic Agent process and any sub-processes it created (such as Beats).
Linux or macOS:
Run the following command to get the ID of the elastic-agent process:
ps | grep elastic-agent
Then kill the process:
kill -9 PID
Where PID is the ID of the elastic-agent process.
Systemd:
The DEB and RPM packages include a service unit for Linux systems with systemd.
On these systems, you can manage Elastic Agent by using systemd commands. Use
systemctl to stop the Agent:
systemctl stop elastic-agent