- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Step 1: Installing Filebeat
- Step 2: Configuring Filebeat
- Step 3: Configuring Filebeat to Use Logstash
- Step 4: Loading the Index Template in Elasticsearch
- Step 5: Starting Filebeat
- Step 6: Loading the Kibana Index Pattern
- Quick Start for Common Log Formats
- Command Line Options
- Directory Layout
- Repositories for APT and YUM
- Running Filebeat on Docker
- Upgrading Filebeat
- How Filebeat Works
- Configuring Filebeat
- Modules
- Exported Fields
- Securing Filebeat
- Troubleshooting
- Migrating from Logstash Forwarder to Filebeat
WARNING: Version 5.6 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.
Migrating from Logstash Forwarder to Filebeat
editMigrating from Logstash Forwarder to Filebeat
editFilebeat is based on the Logstash Forwarder source code and replaces Logstash Forwarder as the method to use for tailing log files and forwarding them to Logstash.
Filebeat introduces the following major changes:
- The config file was restructured and converted from JSON to YAML.
- The registry file, which stores the state of the currently read files, was changed.
- Command line options were removed and moved to the configuration file.
- Configuration options for outputs are now inherited from libbeat. For details, see the Beats Platform Reference.
- The Beats input plugin for Logstash is required.
The following topics describe how to migrate from Logstash Forwarder to Filebeat:
Was this helpful?
Thank you for your feedback.