Now at product env. When I restart es(filebeat is still running), I will meet an issue that filebeat doesn't send the log info to es. one line log is too large(7K) may cause this issue?
the filebeat.yml
-
type: log
ignore_older: 48h
close_inactive: 2h
close_timeout: 10m
clean_inactive: 72h -
output.elasticsearch:
max_retries: 2
timeout: 300
Version: filebeat 6.2.3
Operating System: CentOS release 6.8