# Kibana conflict type field

**URL:** https://discuss.elastic.co/t/kibana-conflict-type-field/270667
**Category:** Kibana
**Tags:** ilm-index-lifecycle-management
**Created:** [April 20, 2021, 7:38am UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667 "2021-04-20T07:38:51Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![devon.thomson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/devon.thomson/32/85468_2.png) [@devon.thomson](https://discuss.elastic.co/u/devon.thomson)
#### Post date: [April 20, 2021, 4:09pm UTC](https://discuss.elastic.co/t/kibana-conflict-type-field/270667/2 "2021-04-20T16:09:58Z")

</div>

Hi @nazakat,

It looks like you may need to reindex one or more of the indices that make up this index pattern to resolve the conflict. See this previous discuss thread for more information:

> [@How to fix mapping conflict?](https://discuss.elastic.co/t/how-to-fix-mapping-conflict/55072):
>
> I have a few fields (bytesSent, bytesReceived, timetaken) that show mapping conflicts, and thus I cannot visualize them in Kibana. All of these log entries are going to an index "logstash-\*" I am pretty green at this, so how would I go about finding all of the conflicting indexes and fixing or removing them? Here is part of the grok expression used for these conflicting fields in Logstash: %{NUMBER:bytesSent} %{NUMBER:bytesReceived} %{NUMBER:timetaken} And then a mutate (is this even necess…

---

_[View the full topic](https://discuss.elastic.co/t/kibana-conflict-type-field/270667)._