Filebeat documentation is very clear that logs not ending in a newline character will not be processed by filebeat: Documentation
I do however have a number of logs which are written as single JSON objects, in a single line, which does not terminate with a newline character. I am unable to change the logger to add this newline character.
Has anyone found any solutions to forcing filebeat to read this?
close_eof or multiline options don't appear to work, and I believe it's the line isn't read into the buffer until the newline character is read? So it will open and close the harvester but nothing has ever been read into the buffer.
Any help would be appreciated.