Removing the content of this topic because it is not an elastic issue. But for anyone else who comes across this: Logs should be written to disk with \n for new lines, not \\n, and Kibana will read appropriately.

Remove \n Characters in Filebeat

tudor (Tudor Golubenco) July 26, 2017, 9:06am 2

Filebeat doesn't have support for string replacement, but you can do it either with Ingest Node (gsub processor), or with Logstash.

Topic		Replies	Views
Filebeat escaping backslashes on its own Beats filebeat	9	4060	July 6, 2016
Removing of \\\\ via filebeat while parsing logs to elastic search Beats filebeat	3	450	December 10, 2020
Filebeat Line Endings Problem '\n' Beats filebeat	6	1822	December 19, 2018
Multiline txt log files not parsing correctly in ingest pipeline Beats filebeat	1	316	May 21, 2020
Filebeat with new line Beats	4	1574	June 1, 2018

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Remove \n Characters in Filebeat

Related topics