Filebeat tail not working when file timestamp is not updated

We have a Tuxedo application server that write logs files, but the log file timestamp is only updated when the file rolls over each night. The log file is actively written to and if you open the file you can see the new data. I haven't been able to get Filebeat to read the file during the day. Once the system rolls over to new and closes it (thus updating the timestamp) Filebeat will pick up the changes. I've tried setting tail_files: true as well, but even that waits for the timestamp to update.

Is there a way to get Filebeat to look at the content length of the file when determining if there is new data to process?

Which filebeat version are you using? Can you share your config file?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.