# Filebeat console repeat logs for filestream input

**URL:** <https://discuss.elastic.co/t/filebeat-console-repeat-logs-for-filestream-input/295435>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 26, 2022, 9:11am UTC](https://discuss.elastic.co/t/filebeat-console-repeat-logs-for-filestream-input/295435 "2022-01-26T09:11:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhiweiv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhiweiv/32/70217_2.png) [@zhiweiv](https://discuss.elastic.co/u/zhiweiv)\
**Post date:** [January 26, 2022, 9:11am UTC](https://discuss.elastic.co/t/filebeat-console-repeat-logs-for-filestream-input/295435/1 "2022-01-26T09:11:12Z")

</div>

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

```auto
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?

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [January 26, 2022, 1:18pm UTC](https://discuss.elastic.co/t/filebeat-console-repeat-logs-for-filestream-input/295435/2 "2022-01-26T13:18:32Z")

</div>

Hi,

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

---

<div class="post-metadata">

**Author:** ![zhiweiv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhiweiv/32/70217_2.png) [@zhiweiv](https://discuss.elastic.co/u/zhiweiv)\
**Post date:** [January 27, 2022, 12:26am UTC](https://discuss.elastic.co/t/filebeat-console-repeat-logs-for-filestream-input/295435/3 "2022-01-27T00:26:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 24, 2022, 2:26am UTC](https://discuss.elastic.co/t/filebeat-console-repeat-logs-for-filestream-input/295435/4 "2022-02-24T02:26:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.