- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Upgrading Filebeat
- How Filebeat Works
- Configuring Filebeat
- Configuration Options (Reference)
- Filebeat Prospectors Configuration
- Filebeat Global Configuration
- General Configuration
- Elasticsearch Output Configuration
- Logstash Output Configuration
- Kafka Output Configuration
- Redis Output Configuration
- File Output Configuration
- Console Output Configuration
- SSL Configuration
- Paths Configuration
- Logging Configuration
- Processors
- Filtering and Enhancing the Exported Data
- Managing Multiline Messages
- Configuring Filebeat to Use Ingest Node
- Using Environment Variables in the Configuration
- Specifying Multiple Prospectors
- Load Balancing
- YAML Tips and Gotchas
- Regular Expression Support
- Configuration Options (Reference)
- Exported Fields
- Securing Filebeat
- Troubleshooting
- Migrating from Logstash Forwarder to Filebeat
WARNING: Version 5.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.
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.