- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick start: Get logs, metrics, and uptime data into the Elastic Stack
- Quick start: Get application traces into the Elastic Stack
- Elastic Agents
- Install Elastic Agents
- Uninstall Elastic Agent
- Run Elastic Agent standalone (advanced users)
- Run Elastic Agent in a container
- Run Elastic Agent standalone on Kubernetes
- Upgrade Elastic Agent
- Start Elastic Agent
- Stop Elastic Agent
- Unenroll Elastic Agent
- View status of Elastic Agents
- Variables and conditions in input configurations
- Environment variables
- Configure logging for Fleet-managed Elastic Agents
- Policies
- Elastic Agent standalone configuration
- Fleet UI settings
- Fleet Server
- Fleet enrollment tokens
- Encrypt traffic in a self-managed cluster
- Data streams
- Command reference
- Troubleshoot common problems
- Frequently asked questions
- Release notes
- Fleet APIs
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Start Elastic Agent
editStart Elastic Agent
editIf you’ve stopped the Elastic Agent service and want to restart it, use the commands that work with your system:
sudo launchctl load /Library/LaunchDaemons/co.elastic.elastic-agent.plist
sudo service elastic-agent start
Start-Service elastic-agent
The DEB package includes a service unit for Linux systems with systemd. On these systems, you can manage Elastic Agent by using the usual systemd commands.
Use systemctl
to start the agent:
sudo systemctl start elastic-agent
Otherwise, use:
sudo service elastic-agent start
The RPM package includes a service unit for Linux systems with systemd. On these systems, you can manage Elastic Agent by using the usual systemd commands.
Use systemctl
to start the agent:
sudo systemctl start elastic-agent
Otherwise, use:
sudo service elastic-agent start
Was this helpful?
Thank you for your feedback.