Filebeat and systemd
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
The DEB and RPM packages include a service unit for Linux systems with systemd. On these systems, you can manage Filebeat by using the usual systemd commands.
The service unit is configured with UMask=0027 which means the most permissive mask allowed for files created by Filebeat is 0640. All configured file permissions higher than 0640 will be ignored. Please edit the unit file manually in case you need to change that.
Use systemctl to start or stop Filebeat:
sudo systemctl start filebeat
sudo systemctl stop filebeat
By default, the Filebeat service starts automatically when the system boots. To enable or disable auto start use:
sudo systemctl enable filebeat
sudo systemctl disable filebeat
To get the service status, use systemctl:
systemctl status filebeat
Logs are stored by default in journald. To view the Logs, use journalctl:
journalctl -u filebeat.service
The systemd service unit file includes environment variables that you can override to change the default options.
| Variable | Description | Default value |
|---|---|---|
| BEAT_LOG_OPTS | Log options | |
| BEAT_CONFIG_OPTS | Flags for configuration file path | -c /etc/filebeat/filebeat.yml |
| BEAT_PATH_OPTS | Other paths | --path.home /usr/share/filebeat --path.config /etc/filebeat --path.data /var/lib/filebeat --path.logs /var/log/filebeat |
You can use BEAT_LOG_OPTS to set debug selectors for logging. However, to configure logging behavior, set the logging options described in Configure logging.
To override these variables, create a drop-in unit file in the /etc/systemd/system/filebeat.service.d directory.
For example a file with the following content placed in /etc/systemd/system/filebeat.service.d/debug.conf would override BEAT_LOG_OPTS to enable debug for Elasticsearch output.
[Service]
Environment="BEAT_LOG_OPTS=-d elasticsearch"
To apply your changes, reload the systemd configuration and restart the service:
systemctl daemon-reload
systemctl restart filebeat
It is recommended that you use a configuration management tool to include drop-in unit files. If you need to add a drop-in manually, use systemctl edit filebeat.service.