Out-of-the-box integrations use legacy mapping types in their component templates.
If you enable the mapper_size plugin, then go to apply it in .fleet_globals, this error message occurs:
Unable to create component template updating component template [.fleet_globals-1] results in invalid composable template [COMPONENT-TEMPLATES-HERE-PER-EACH-INTEGRATION] after templates are merged
Then go look at the specific integration component template mapping section:
If an Elastic-Agent was installed, .fleet_globals was modified to display the _size field, then that agent will not upgrade and be stuck on that version.
Out-of-the-box integrations use legacy mapping types in their component templates.
If you enable the mapper_size plugin, then go to apply it in .fleet_globals, this error message occurs:
Unable to create component template updating component template [.fleet_globals-1] results in invalid composable template [COMPONENT-TEMPLATES-HERE-PER-EACH-INTEGRATION] after templates are merged
Then go look at the specific integration component template mapping section:![image](https://github.com/elastic/ecs/assets/11168913/502c8eab-ed3c-45d4-a270-d8a2178c4e68)
Link goes here from component template: https://www.elastic.co/guide/en/elasticsearch/reference/8.11/removal-of-types.html
If an Elastic-Agent was installed, .fleet_globals was modified to display the _size field, then that agent will not upgrade and be stuck on that version.