# Problem indexing mapper\_parsing\_exception

**URL:** <https://discuss.elastic.co/t/problem-indexing-mapper-parsing-exception/140822>\
**Category:** Logstash\
**Created:** [July 20, 2018, 2:07am UTC](https://discuss.elastic.co/t/problem-indexing-mapper-parsing-exception/140822 "2018-07-20T02:07:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![joshsmoore](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshsmoore/32/31581_2.png) [@joshsmoore](https://discuss.elastic.co/u/joshsmoore)\
**Post date:** [July 20, 2018, 2:07am UTC](https://discuss.elastic.co/t/problem-indexing-mapper-parsing-exception/140822/1 "2018-07-20T02:07:00Z")

</div>

I am placing this in Logstash because I think the problem is in the log stash processing even though it is raised by Elasticsearch. This is the exception I am seeing:

central\_logger\_logstash.1.iz1mulhde4jx@logger-swarm1 | [2018-07-20T02:00:29,078][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"logstash-6.3.0-2018.07.20", :\_type=\>"doc", :\_routing=\>nil}, #LogStash::Event:0x66c1b75b], :response=\>{"index"=\>{"\_index"=\>"logstash-6.3.0-2018.07.20", "\_type"=\>"doc", "\_id"=\>"1mVqtWQBG03hsxOZvSTv", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"object mapping for [host] tried to parse field [host] as object, but found a concrete value"}}}}

Can anybody point me to how to log the actual document that is causing the problem so I can see where it is coming from?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 20, 2018, 6:38am UTC](https://discuss.elastic.co/t/problem-indexing-mapper-parsing-exception/140822/2 "2018-07-20T06:38:49Z")

</div>

If you google the error message ("object mapping for [host] tried to parse field [host] as object, but found a concrete value") you'll find previous posts about this topic.

> Can anybody point me to how to log the actual document that is causing the problem so I can see where it is coming from?

If you enable the dead letter queue feature Logstash will save rejected events to a file. You can then use a dead\_letter\_queue input to read from that file and do whatever with the events. See [Dead letter queues (DLQ) | Logstash Reference [8.11] | Elastic](https://www.elastic.co/guide/en/logstash/current/dead-letter-queues.html).

---

<div class="post-metadata">

**Author:** ![joshsmoore](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshsmoore/32/31581_2.png) [@joshsmoore](https://discuss.elastic.co/u/joshsmoore)\
**Post date:** [July 24, 2018, 2:19pm UTC](https://discuss.elastic.co/t/problem-indexing-mapper-parsing-exception/140822/3 "2018-07-24T14:19:28Z")

</div>

That helped me fix it. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 21, 2018, 2:20pm UTC](https://discuss.elastic.co/t/problem-indexing-mapper-parsing-exception/140822/4 "2018-08-21T14:20:58Z")

</div>

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