mapper_parsing_exception "failed to parse field [host] of type [text]"

[opoplawski]

Get lots of:

``
logstash[20807]: [2019-01-25T15:27:15,753][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"logstash-dns-2019.01.25", :_type=>"doc", :routing=>nil}, #LogStash::Event:0x65e65681], :response=>{"index"=>{"_index"=>"logstash-dns-2019.01.25", "_type"=>"doc", "_id"=>"gy1Wh2gBNsyAfm1OvkqE", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse field [host] of type [text]", "caused_by"=>{"type"=>"illegal_state_exception", "reason"=>"Can't get text on a START_OBJECT at 1:939"}}}}}

This seems to be because beats now use "host.ip"/"host.name" and so forth now - https://www.elastic.co/guide/en/beats/libbeat/current/breaking-changes-6.3.html

[opoplawski]

Hmm, this might be an issue with my using two different versions of beats (6.2.4 and 6.4.2).

[opoplawski]

Also see want seems to be caused by the opposite expectation for host:

logstash[6183]: [2019-01-25T15:31:54,917][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"logstash-2019.01.25", :_type=>"doc", :routing=>nil}, #<LogStash::Event:0xfb3cfa0>], :response=>{"index"=>{"_index"=>"logstash-2019.01.25", "_type"=>"doc", "_id"=>"1i1bh2gBNsyAfm1OAHDO", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"object mapping for [host] tried to parse field [host] as object, but found a concrete value"}}}}

[pevma]

Do you use the SELKS5 ES/LS templates or your own custom ones ?

…

-- Regards, Peter Manev On 26 Jan 2019, at 00:36, Orion Poplawski ***@***.***> wrote: Also see want seems to be caused by the opposite expectation for host: logstash[6183]: [2019-01-25T15:31:54,917][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"logstash-2019.01.25", :_type=>"doc", :routing=>nil}, #<LogStash::Event:0xfb3cfa0>], :response=>{"index"=>{"_index"=>"logstash-2019.01.25", "_type"=>"doc", "_id"=>"1i1bh2gBNsyAfm1OAHDO", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"object mapping for [host] tried to parse field [host] as object, but found a concrete value"}}}} — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.