Metricbeat 6.3.2 upgrade breaks?

Elastic Stack Beats
10

I should be more specific about what happens here. The old Metricbeat template causes new data to have the wrong mapping. If preserving data is required, then these steps should work:

  1. place a write block on the "bad" metricbeat-<version>.* index with index.blocks.write: true
  2. delete the old template
  3. reindex the bad index it to an index with a different name
  4. delete the bad index

The new Metricbeat will then be free to index to metricbeat-<version> without a mapping conflict.