-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add FAQ topic that explains how to get Filebeat to re-process log files #1595
Comments
@dedemorton We should be careful with the word "parse" as Filebeat does not parse log lines. |
Closing in favor of tracking this issue in #2482 |
Ehuuu anyone care to answer the question ??? Update: Please help. |
@chrisribe Please post any questions to the Filebeat discussion forum, not Github. To be honest it's not clear to me what you're trying to do. If you want to get Filebeat to reprocess all your log files, just delete the registry file in the data folder. See Directory layout if you need help finding the registry file. If you need to know something else, post a question to the discussion forum. |
Hi dedemotron, Sorry for posting on a closed topic. After searching google this post was the best result I could find. I did not see the filebeat forum. The docs are clearly missing this detail, it's something any dev will need to do after testing filebeat. Thanks |
Add "how do I get Filebeat to re-process log files" to the FAQ. See related discussion in the forums here: https://discuss.elastic.co/t/how-do-i-reset-the-file-pointer-in-filebeats/49440
The text was updated successfully, but these errors were encountered: