Start Heartbeat by issuing the appropriate command for your platform. If you are accessing a secured Elasticsearch cluster, make sure you’ve configured credentials as described in Step 2: Configure Heartbeat.
If you use an init.d script to start Heartbeat on deb or rpm, you can’t specify command line flags (see Command reference). To specify flags, start Heartbeat in the foreground.
deb and rpm:
sudo service heartbeat-elastic start
mac and linux:
You’ll be running Heartbeat as root, so you need to change ownership of the
configuration file, or run Heartbeat with
To have launchd start
elastic/tap/heartbeat and then restart it at login,
brew services start elastic/tap/heartbeat-full
To run Heartbeat in the foreground instead of running it as a background service, run:
You’ll be running Heartbeat as root, so you need to change ownership
of the configuration file, or run Heartbeat with
PS C:\Program Files\Heartbeat> Start-Service heartbeat
By default, Windows log files are stored in
Heartbeat is now ready to check the status of your services and send events to your defined output.