filebeat truncated log file line accidentally, so when parsing the next line, error happend Filebeat error log 2020-04-28T16:50:37.642+0800 ERROR readjson/json.go:52 Error decoding JSON: invalid character 'e' in literal true (expecting 'r') some correct line in files like below: {"#ac…

Filebeat seems truncated message in single line[Filebeat 7.6]

system (system) Closed May 28, 2020, 2:17am 4

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

Topic		Replies	Views
Filebeat truncates output data Beats filebeat	8	2082	January 2, 2020
Filebeat / logstash truncating json log lines Beats filebeat	8	3238	May 17, 2017
Filebeats cuts off first part of log event Beats	5	2289	December 12, 2018
Filebeat-5.5.1 got decoding JSON with a simple json line string Beats filebeat	2	593	September 7, 2017
Filebeat not ingesting JSON Beats filebeat	3	771	July 11, 2019

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.

Filebeat seems truncated message in single line[Filebeat 7.6]

Related topics