IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Step 4: Set up the Kibana dashboards Step 6: View the sample Kibana dashboards »
Elastic Docs ›Heartbeat Reference [7.7] ›Get started with Heartbeat

Step 5: Start Heartbeat

edit

Step 5: Start Heartbeat

edit

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:

sudo chown root heartbeat.yml 
sudo ./heartbeat -e

You’ll be running Heartbeat as root, so you need to change ownership of the configuration file, or run Heartbeat with --strict.perms=false specified. See Config File Ownership and Permissions in the Beats Platform Reference.

brew:

To have launchd start elastic/tap/heartbeat and then restart it at login, run:

brew services start elastic/tap/heartbeat-full

To run Heartbeat in the foreground instead of running it as a background service, run:

sudo chown root /usr/local/etc/heartbeat/beatname_lc.yml 
sudo heartbeat -e

You’ll be running Heartbeat as root, so you need to change ownership of the configuration file, or run Heartbeat with --strict.perms=false specified. See Config File Ownership and Permissions in the Beats Platform Reference.

win:

PS C:\Program Files\Heartbeat> Start-Service heartbeat

By default, Windows log files are stored in C:\ProgramData\heartbeat\Logs.

Heartbeat is now ready to check the status of your services and send events to your defined output.

« Step 4: Set up the Kibana dashboards Step 6: View the sample Kibana dashboards »