Start Filebeat
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Before starting Filebeat:
- Follow the steps in Quick start: installation and configuration to install, configure, and set up the Filebeat environment.
- Make sure Kibana and Elasticsearch are running.
- Make sure the user specified in
filebeat.ymlis authorized to publish events.
To start Filebeat, run:
sudo service filebeat start
If you use an init.d script to start Filebeat, you can’t specify command line flags (see Command reference). To specify flags, start Filebeat in the foreground.
Also see Filebeat and systemd.
sudo service filebeat start
If you use an init.d script to start Filebeat, you can’t specify command line flags (see Command reference). To specify flags, start Filebeat in the foreground.
Also see Filebeat and systemd.
sudo chown root filebeat.yml
sudo chown root modules.d/{modulename}.yml
sudo ./filebeat -e
- You’ll be running Filebeat as root, so you need to change ownership of the configuration file and any configurations enabled in the
modules.ddirectory, or run Filebeat with--strict.perms=falsespecified. See Config File Ownership and Permissions.
sudo chown root filebeat.yml
sudo chown root modules.d/{modulename}.yml
sudo ./filebeat -e
- You’ll be running Filebeat as root, so you need to change ownership of the configuration file and any configurations enabled in the
modules.ddirectory, or run Filebeat with--strict.perms=falsespecified. See Config File Ownership and Permissions.
PS C:\Program Files\filebeat> Start-Service filebeat
By default Windows log files are stored in C:\Program Files\Filebeat-Data\logs.
In versions before 9.0.6, the default location for Windows log files was C:\ProgramData\filebeat\logs.