# Mapping conflict for system.process.cpu.system+user when using metricbeat-6.3.0 and 6.6.0

**URL:** <https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [April 2, 2019, 1:17pm UTC](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999 "2019-04-02T13:17:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaem2111](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaem2111/32/24961_2.png) [@kaem2111](https://discuss.elastic.co/u/kaem2111)\
**Post date:** [April 2, 2019, 1:17pm UTC](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999/1 "2019-04-02T13:17:02Z")

</div>

I got a mapping conflict in Kibana index patterns due to different templates definitions for same field provided during beat installation.

 ![mapping_conflict](https://us1.discourse-cdn.com/elastic/original/3X/d/2/d25ef40c3dce4d2fb0364bf0202a5db0f31d3856.gif)

How can I fix that?

How will you handle this with ECS?

---

<div class="post-metadata">

**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\
**Post date:** [April 9, 2019, 11:24pm UTC](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999/2 "2019-04-09T23:24:09Z")

</div>

@kaem2111 Sorry for the late response. The easiest way is to delete the existing two templates and create a fresh new one. I see in [Metricbeat 6.3.2 upgrade breaks?](https://discuss.elastic.co/t/metricbeat-6-3-2-upgrade-breaks/142241/10?u=kaiyan_sheng), there is also a way to actually preserve data if that will be more helpful.

---

<div class="post-metadata">

**Author:** ![kaem2111](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaem2111/32/24961_2.png) [@kaem2111](https://discuss.elastic.co/u/kaem2111)\
**Post date:** [April 16, 2019, 8:56am UTC](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999/3 "2019-04-16T08:56:23Z")

</div>

@Kaiyan_Sheng Unfortunaly the hint doesn't help, because I have still installed Metricbeat agent for both release in parallel (see above: both indices are from same day).

If I remember correclty, you wanted to be compatible within all minor releases and even the next major release.

Does this mean, I have to upgrade all 'old' beat agents to get rid of this conflict?

Will this issue be obsolete, when using ECS?

---

<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:** [May 14, 2019, 9:00am UTC](https://discuss.elastic.co/t/mapping-conflict-for-system-process-cpu-system-user-when-using-metricbeat-6-3-0-and-6-6-0/174999/4 "2019-05-14T09:00:09Z")

</div>

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