Does Filebeat logs fills up the disk?

Elastic Stack Beats
1

  1. why the filebeat is generating the logs like filebeat , filbeat.1 , filebeat.2 ?

  2. "filebeat " log file created by filebeat as it runs showing what is doing.That kind of continuing content will eventually create a very large file and possibly fill up a file system ?
    2019-07-09T15:50:28Z INFO No non-zero metrics in the last 30s
    2019-07-09T15:50:58Z INFO No non-zero metrics in the last 30s
    2019-07-09T15:51:28Z INFO No non-zero metrics in the last 30s
    2019-07-09T15:51:37Z ERR Connecting error publishing events (retrying): dial tcp 10.8.93.204:5044: i/o timeout
    2019-07-09T15:51:58Z INFO No non-zero metrics in the last 30s
    2019-07-09T15:50:28Z INFO No non-zero metrics in the last 30s
    2019-07-09T15:50:58Z INFO No non-zero metrics in the last 30s
    2019-07-09T15:51:28Z INFO No non-zero metrics in the last 30s
    10.8.93.204:5044: i/o timeout
    2019-07-09T15:51:58Z INFO No non-zero metrics in the last 30s

2

It created a new log each time it runs, and rolls them 1....7 here. I've never had it fill the disk (unlike logstash and elasticsearch).

FYI, if you run filebeat commands like filebeat modules list, it may create another log and the service filebeat may be updating a .1 or later version.

3

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