I am using heartbeat 6.2.2, logstash 6.2.3, elasticsearch 6.2.3 When sending heartbeat tcp monitor data to logstash, i get the following error message: [2018-06-28T00:57:22,253][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>n…

managed to track it down. looks like previous iterations of the indices had that field as a vector, instead of object. had to stop all log flow, remove all old indices, remove kibana index patterns, restart log flow, have the index create correctly and then re-create kibana index pattern for the gro…

"object mapping for [monitor] tried to parse field [monitor] as object, but found a concrete value"

Elastic Stack Logstash

system (system) Closed July 26, 2018, 11:30pm 3

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

Topic		Replies	Views
"reason"=>"object mapping for [host] tried to parse field [host] as object, but found a concrete value" Logstash	6	9322	May 19, 2021
Tried to parse field as object, but found a concrete value Logstash	3	66501	May 20, 2020
Mapper_parsing_exception Using GelfD and Logstash Logstash	5	514	September 6, 2018
Object mapping errors Logstash	7	1883	December 23, 2021
Logstash unable to map field to es Logstash	6	874	September 6, 2018

"object mapping for [monitor] tried to parse field [monitor] as object, but found a concrete value"

Related topics