Directory layout
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 directory layout of an installation is as follows:
Archive installation has a different layout. See zip, tar.gz, or tgz.
| Type | Description | Default Location | Config Option |
|---|---|---|---|
| home | Home of the Filebeat installation. | path.home |
|
| bin | The location for the binary files. | {path.home}/bin |
|
| config | The location for configuration files. | {path.home} |
path.config |
| data | The location for persistent data files. | {path.home}/data |
path.data |
| logs | The location for the logs created by Filebeat. | {path.home}/logs |
path.logs |
You can change these settings by using CLI flags or setting path options in the configuration file.
Filebeat uses the following default paths unless you explicitly change them.
| Type | Description | Location |
|---|---|---|
| home | Home of the Filebeat installation. | /usr/share/filebeat |
| bin | The location for the binary files. | /usr/share/filebeat/bin |
| config | The location for configuration files. | /etc/filebeat |
| data | The location for persistent data files. | /var/lib/filebeat |
| logs | The location for the logs created by Filebeat. | /var/log/filebeat |
For the deb and rpm distributions, these paths are set in the init script or in the systemd unit file. Make sure that you start the Filebeat service by using the preferred operating system method (init scripts or systemctl). Otherwise the paths might be set incorrectly.
| Type | Description | Location |
|---|---|---|
| home | Home of the Filebeat installation. | /usr/share/filebeat |
| bin | The location for the binary files. | /usr/share/filebeat |
| config | The location for configuration files. | /usr/share/filebeat |
| data | The location for persistent data files. | /usr/share/filebeat/data |
| logs | The location for the logs created by Filebeat. | /usr/share/filebeat/logs |
| Type | Description | Location |
|---|---|---|
| home | Home of the Filebeat installation. | {extract.path} |
| bin | The location for the binary files. | {extract.path} |
| config | The location for configuration files. | {extract.path} |
| data | The location for persistent data files. | {extract.path}/data |
| logs | The location for the logs created by Filebeat. | {extract.path}/logs |
For the zip, tar.gz, or tgz distributions, these paths are based on the location of the extracted binary file. This means that if you start Filebeat with the following simple command, all paths are set correctly:
./filebeat