Hello, I have a problem I've verified in filebeat 6.8.3, 7.5.1, and 7.16.3 I have a filebeat.yml filebeat.inputs, type log, with three configured paths with ** in the middle portions, something like - /var/log/a/b/**/ONE - /var/log/a/b/**/TWO - /var/log/a/b/**/THREE and on filebeat startup…

Harvester not started for new files in configured paths

dchsueh (Daniel Hsueh) January 24, 2022, 5:31pm 3

Anybody have any ideas?
I realize this works for most people; for me in some environments it seems to work reliably but in others never.

Topic		Replies	Views
Filebeats not harvesting new file Beats filebeat	5	2422	February 8, 2019
fileBeat isn't harvesting the logs from the last path's Beats filebeat	9	3680	December 27, 2017
Harvester could not be started on new file Beats	1	1031	March 2, 2020
Filebeat harvester dont started on files Beats filebeat	5	5312	May 28, 2018
Harvester doesnt read file Beats filebeat	2	487	November 19, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Harvester not started for new files in configured paths

Related topics