# This error seems to be related to mapping issues in Elasticsearch, 

**URL:** <https://discuss.elastic.co/t/this-error-seems-to-be-related-to-mapping-issues-in-elasticsearch/346427>\
**Category:** Logstash\
**Created:** [November 4, 2023, 11:01am UTC](https://discuss.elastic.co/t/this-error-seems-to-be-related-to-mapping-issues-in-elasticsearch/346427 "2023-11-04T11:01:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesjames](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@jamesjames](https://discuss.elastic.co/u/jamesjames)\
**Post date:** [November 4, 2023, 11:01am UTC](https://discuss.elastic.co/t/this-error-seems-to-be-related-to-mapping-issues-in-elasticsearch/346427/1 "2023-11-04T11:01:00Z")

</div>

2023-11-04T10:33:48,353][WARN][logstash.outputs.elasticsearch][main]  
Could not index event to Elasticsearch. {:status=\>400, :action=\>["index",  
{:\_id=\>nil, :\_index=\>"staging-2023.11.04", :\_type=\>"\_doc", :routing=\>nil},  
#LogStash::Event:0x4fdc7ef6], :response=\>{"index"=\>{"\_index"=\>"staging-2023.11.04",  
"\_type"=\>"\_doc", "\_id"=\>"adjhghASjfv4456", "status"=\>400, "error"=\>  
{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse field  
[kubernetes.labels.app] of type [text] in document with id 'adjhghASjfv4456'.  
Preview of field's value: '{kubernetes={io/instance=cert-manager, io/component=cainjector,  
io/name=cainjector, io/version=v1.5.4}, value=cainjector}'", "  
caused\_by"=\>{"type"=\>"illegal\_state\_exception",  
"reason"=\>"Can't get text on a START\_OBJECT at 1:1022"}}}}}  
/var/log/logstash$ PUT staging-2023.11.04

Any insights or suggestions on how to resolve this issue would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [November 4, 2023, 1:34pm UTC](https://discuss.elastic.co/t/this-error-seems-to-be-related-to-mapping-issues-in-elasticsearch/346427/2 "2023-11-04T13:34:14Z")

</div>

Hello,

This is a duplicated of this [another post](https://discuss.elastic.co/t/this-error-seems-to-be-related-to-mapping-issues-in-elasticsearch-below-error-found-in-logstash/346414).

Please do not open duplicate posts for the same issue.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 4, 2023, 4:06pm UTC](https://discuss.elastic.co/t/this-error-seems-to-be-related-to-mapping-issues-in-elasticsearch/346427/3 "2023-11-04T16:06:29Z")

</div>

Closed as duplicate.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 4, 2023, 4:06pm UTC](https://discuss.elastic.co/t/this-error-seems-to-be-related-to-mapping-issues-in-elasticsearch/346427/4 "2023-11-04T16:06:34Z")

</div>


