# Logstash error „mapper\_parsing\_exception“

**URL:** https://discuss.elastic.co/t/logstash-error-mapper-parsing-exception/155922
**Category:** Logstash
**Created:** [November 8, 2018, 3:47pm UTC](https://discuss.elastic.co/t/logstash-error-mapper-parsing-exception/155922 "2018-11-08T15:47:08Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![niagato](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@niagato](https://discuss.elastic.co/u/niagato)
#### Post date: [November 8, 2018, 3:47pm UTC](https://discuss.elastic.co/t/logstash-error-mapper-parsing-exception/155922/1 "2018-11-08T15:47:08Z")

</div>

We use an instance of Elastic as part of Security Onion, because of that preconfigured config files exist on the system. Because of that all document fields with the name ‚host‘ will be renamed to ‚beat\_host‘ by Logstash.

Logstash refuses to index, because of a field named „beat\_host“ in the index mapping declared as an object type, but instead of this type it received an concrete value.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/1/31c8ad21b35feac575a2de51b62a8a9810160810.jpeg)

---

<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: [December 6, 2018, 3:47pm UTC](https://discuss.elastic.co/t/logstash-error-mapper-parsing-exception/155922/2 "2018-12-06T15:47:15Z")

</div>

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