Discuss the Elastic Stack

JSON codec polluting logs with ERROR messages if input is plain string

Elastic Stack Logstash

Badger June 5, 2019, 3:46pm 6

Do not use a codec, use a json filter instead, with "message" as the source.

Topic		Replies	Views	Activity
Constant JSON parse errors in logstash output log Logstash	3	6903	April 19, 2017
Logstash JSON codec Logstash	3	1153	July 6, 2017
JSON parse error, original data now in message field, even though its a valid json Logstash	2	14019	October 23, 2018
Unable to avoid JSON parsing errors in logstash log-file Logstash	2	7913	June 9, 2017
Json codec: blank lines make logstash throw errors Logstash	2	1350	July 6, 2017

© 2020. All Rights Reserved - Elasticsearch

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.