Filebeat console repeat logs for filestream input

[zhiweiv]

After switch input type from log to filestream, there are repeat logs every 10s in filebeat console like following:

2022-01-26T09:06:45.287Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:06:55.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:07:05.287Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:07:15.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:07:25.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:07:35.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:07:45.287Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:07:55.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:08:05.287Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:08:15.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:08:25.287Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:08:35.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:08:45.286Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:08:55.287Z [file_watcher] filestream/fswatch.go:137 Start next scan
2022-01-26T09:09:05.287Z [file_watcher] filestream/fswatch.go:137 Start next scan

It seems meaningless, can it be removed?

[mtojek (Marcin Tojek)]

Hi,

AFAIR, it goes with INFO logger, which means that you can consider lowering the logging level from INFO to WARN?

[zhiweiv]

Other INFO level logs are useful, so change log level is not feasible.

Can this type of log be removed from code directly? or change it's level to DEBUG or something else to avoid it appear in default setting.