Hello,

We just upgraded our stack and collectors agents to version 8.18.1 and after that some integrations, after upgrading the Crowdstrike integration we now have mapping conflicts in the data view.

It seems that the conflict was added in this PR #12869

The field was unmapped before and adding explicit mapping resulted in a mapping conflict in Kibana.

Looking at the changelog this was marked as enhancement, not breaking-change, is it possible to future PRs to have both information or this is not supported yet?

Does the integrations have tests coverage for this kind of issue in Kibana? This can be pretty critical depending on which field is affected by the conflict.