[2020-05-18T09:02:52,095][WARN ][logstash.outputs.amazonelasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"gppepo-epo-govpp-scheduler-2020.05.18", :_type=>"_doc", :_routing=>nil}, # LogStash::Event:0x458fc470 ], :response=>{"index"=>{"_index"…

[image] ranjini: if logstash is not able to parse the logs. They will still appear in kibana right with parsefailure If logstash is unable to parse the logs they will still appear. If elasticsearch is unable to parse the logs they will be lost.

Could not index event to Elasticsearch. {:status=>400, :action=> #<LogStash::Event:0x458fc470>], :response=>{"index"=>ception", "reason"=>"failed to parse date field

Elastic Stack Logstash

system (system) Closed June 17, 2020, 4:01pm 5

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

Topic		Replies	Views
"reason"=>"failed to parse field [Time] of type [date] in document with id 'xxxxxxxxxxxxxxx' Logstash	3	14769	April 19, 2021
Logstash couldn't index date field for few log lines Logstash	4	514	July 12, 2019
Could not index event to Elasticsearch. Illegal argument exception Logstash docker	5	2648	October 18, 2019
[2020-05-22T09:04:47,691][WARN ][logstash.outputs.amazonelasticsearch] Could not index event to Elasticsearch Logstash	2	337	June 20, 2020
Elasticsearch failed to parse date field with logstash Logstash	9	24406	July 6, 2017

Could not index event to Elasticsearch. {:status=>400, :action=> #<LogStash::Event:0x458fc470>], :response=>{"index"=>ception", "reason"=>"failed to parse date field

Related topics