Closed todd-bowles-console closed 8 years ago
Have you excluded the possibility that the file input's ignore_older
option (introduced in Logstash 2.2) is the culprit?
So obvious in retrospect. The files being used as input for the tests had last modified dates outside of the range of the ignore_older
default.
Thank you very much for pointing that out.
We use logstash 2.1.0 mostly to process and ship local log files on our servers to a remote logstash endpoint (to eventually end up inside Elasticsearch) on Windows.
I tried to upgrade to 2.4.0 today (to benefit from the improved performance and deal with an issue where logstash consumed a vast amount of memory because a lot of files were being generated) and no matter what I did I could not get any files to process in our tests.
We wrap logstash in some Powershell (for various reasons) and generally deploy it with NSSM to have it run as a service. We write tests in Powershell using Pester to validate that our configurations are processing the files as we expect them too.
I'm happy to make our particular solution available for investigation on request, but I don't want to attach it publicly here.
I have attached the configs that I am using.
We're executing them (indirectly) using:
logstash.bat agent -f C:\dev\repository\src\test-working\20160928170845\config*.conf --debug
ap.logshipper.txt output-logs-directory-file.txt