# Mapping Conflict between modules

**URL:** <https://discuss.elastic.co/t/mapping-conflict-between-modules/209707>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 27, 2019, 2:49pm UTC](https://discuss.elastic.co/t/mapping-conflict-between-modules/209707 "2019-11-27T14:49:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarcusCaepio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcuscaepio/32/32458_2.png) [@MarcusCaepio](https://discuss.elastic.co/u/MarcusCaepio)\
**Post date:** [November 27, 2019, 2:49pm UTC](https://discuss.elastic.co/t/mapping-conflict-between-modules/209707/1 "2019-11-27T14:49:52Z")

</div>

Hi all,  
I am just testing Elastic Stack 7.4.2 with SIEM.  
I am using Filebeat module system and cisco.  
When using "filebeat-\*" as index pattern, kibana tells me, that there is a mapping conflict. The conflicting field is "source.ip"  
I am already dividing the data in indeces like "filebeat-yyyy.mm.dd" and "cisco-asa-yyyy.mm.dd" but the probleme here is, that the imported dashboards are not working with the cisco indeces.

Anybody an idea, how to solve this?

Cheers,  
Marcus

---

<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 25, 2019, 2:49pm UTC](https://discuss.elastic.co/t/mapping-conflict-between-modules/209707/2 "2019-12-25T14:49:54Z")

</div>

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