"error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse [datetime]", "caused_by"=>{"type"=>"illegal_state_exception", "reason"=>"Can't get text on a START_OBJECT at 1:688"}}
Why keep it around if you don't use it? It looks like the field is mapped as a text field but the datetime field of an event you're trying to send to ES actually contains an object.
Um, wait. The error occurs when the JSON string is being parsed, and at that point there is no MSEC field. The JSON spec doesn't allow octal numbers so Logstash is correctly rejecting the bad input.
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.