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

@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?, there is also a way to actually preserve data if that will be more helpful.