WARNING: Version 6.2 of Filebeat has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Step 5: Set up the Kibana dashboards Step 7: View the sample Kibana dashboards »
Elastic Docs ›Filebeat Reference [6.2] ›Getting Started With Filebeat

Step 6: Start Filebeat

edit

Step 6: Start Filebeat

edit

Start Filebeat 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 Filebeat.

If you use an init.d script to start Filebeat on deb or rpm, you can’t specify command line flags (see Command reference). To specify flags, start Filebeat in the foreground.

deb:

sudo service filebeat start

rpm:

sudo service filebeat start

docker:

docker run docker.elastic.co/beats/filebeat:6.2.4

mac:

sudo chown root filebeat.yml 
sudo ./filebeat -e -c filebeat.yml -d "publish"

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

win:

PS C:\Program Files\Filebeat> Start-Service filebeat

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

Filebeat is now ready to send log files to your defined output.

« Step 5: Set up the Kibana dashboards Step 7: View the sample Kibana dashboards »