Filebeat is not able to parse json from files where \n separated json lines (events) are written

I have a log source that generates json log files with excess line feeds.

I can get around this (partially) by adding exclude_lines: ['^$'] as suggested here:

This solves the problem on the logstash/ES side, but syslog where file beats is running is completely filled with

2019-07-30T14:45:41.319Z#011ERROR#011readjson/json.go:52#011Error decoding JSON: EOF

See also:

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