# Mapper\_parsing\_exception error on logstash

**URL:** https://discuss.elastic.co/t/mapper-parsing-exception-error-on-logstash/138012
**Category:** Logstash
**Created:** [June 29, 2018, 5:03pm UTC](https://discuss.elastic.co/t/mapper-parsing-exception-error-on-logstash/138012 "2018-06-29T17:03:27Z")
**Posts on this page:** 1
**Showing post:** 3

<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 2, 2018, 3:54pm UTC](https://discuss.elastic.co/t/mapper-parsing-exception-error-on-logstash/138012/3 "2018-07-02T15:54:30Z")

</div>

> [@Logstash errors after upgrading to filebeat-6.3.0](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984):
>
> After upgrading from filebeat-6.2.4 to filebeat-6.3.0 none of my log messages make into logstash. I did not make any filebeat.yml or logstash.conf changes during the upgrade. The logstash.stdout is full of errors like this... [2018-06-14T16:36:44,073][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"logstash-2018.06.14", :\_type=\>"doc", :\_routing=\>nil}, #\<LogStash::E vent:0x7915b5b2\>], :response=\>{"index"=\>{"…

---

_[View the full topic](https://discuss.elastic.co/t/mapper-parsing-exception-error-on-logstash/138012)._