- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Configuring Filebeat
- Troubleshooting
- Getting Help
- Debugging
- Frequently Asked Questions
- Why can’t I read log files from network volumes?
- Why isn’t Filebeat collecting lines from my file?
- Why is Filebeat using too much CPU?
- Why is the dashboard in Kibana breaking up my data fields incorrectly?
- Why doesn’t my connection to Logstash work?
- Why is @metadata missing in Logstash?
- What is the difference between Logstash and Beats?
- Why does my SSL client fail to connect to Logstash?
- Migrating from Logstash Forwarder to Filebeat
- Reference
WARNING: Version 1.1 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.
Updating the Registry File
editUpdating the Registry File
editThe registry file stores the state and location information that Filebeat uses to track
where it was last reading. Under Logstash Forwarder, this file was called .logstash-fowarder. For Filebeat,
the file was renamed. The name varies depending on the package type:
-
.filebeatfor.tar.gzand.tgzarchives -
/var/lib/filebeat/registryfor DEB and RPM packages -
c:\ProgramData\filebeat\registryfor the Windows zip file
For enhancement reasons, especially for Windows, the structure of the registry file has changed. This makes migrating the file complex and leads to potential errors.
Instead of migrating the registry file, we recommend that you start Filebeat on
the same host where Logstash Forwarder is running, and send the log files to a
different index. This will start indexing from scratch. If you want to start
reading at the end of all files, you can set the tail_files option in the
Filebeat configuration file to true.
Using this approach allows you to keep the old Logstash Forwarder running and then slowly migrate over to Filebeat.