I've got a problem related to log rotation and registry clean up.
This is how the rotation works: after reaching a certain size, the file "logxxx.log" get renamed in "logxxx-timestamp.log" and a new "logxxx.log" is created.
This is my config (I've tried both alpha5 and alpha6 nightly build on a Windows Server 2000)
Paths that should be crawled and fetched. Glob based paths.
During the day those file are written very often and everything seems fine with my config: the registry get cleaned and in task manager I can see that filebeat mem usage remains constant.
However, during the night, when log files get updated seldomly, this line appears many times in filebeat log files:
ERR File is falling under ignore_older before harvesting is finished. Adjust your close_* settings: d:Logger\logxxx.log
This message is written until morning, when our log files are return to be updated every few seconds, then it dissapears. Although that, now the registry keeps growing bigger and bigger and it seems that in can't be cleaned. If I delete the registry manually, filebeat starts working correctly until the night and so on...
Am I missing something with the config? Should I try setting ignore_older to a value even bigger compared to clean_inactive?
Moreover, is there a parameter to get info about the registry and file handler from the log which is not debug?