I have many servers using filebeat 1.2.3 on windows. It's monitoring about 16 directories with rotating logs in each. Some logs can be rotated within a few seconds others can take longer. The issue I face is that the filebeat process starts to consume 100% cpu but doesn't actually start shipping any new files.
Running with -v -e -d "*" it appears to be stuck on the prospector checking files over and over and not actually shipping anything.
I have to delete the registry to return everything to normal.