# Mapping explosion vs. the filebeat template
**URL:** https://discuss.elastic.co/t/mapping-explosion-vs-the-filebeat-template/295886
**Category:** Elasticsearch
**Created:** [January 31, 2022, 10:49pm UTC](https://discuss.elastic.co/t/mapping-explosion-vs-the-filebeat-template/295886 "2022-01-31T22:49:10Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [January 31, 2022, 10:49pm UTC](https://discuss.elastic.co/t/mapping-explosion-vs-the-filebeat-template/295886/1 "2022-01-31T22:49:10Z")
I'm struggling trying to figure out how to convert from the way we used legacy templates to the new index and component templates. I used to add our own templates with higher priority on top of the supplied filebeat template.
Then I read about mapping explosion and that the default limit for index fields is 1000. The filebeat template I just loaded for 7.16.2 for the Elasticsearch and logstash module results in an index with over 6500 fields.
If component templates are the wave of the future, could Elastic break the supplied filebeat template into components for mapping group, like activemq, agent, apache, auditd, aws-cloudwatch, aws-cloudtrail and so on. Then we could include the parts we want with our indices and reduce the excessive field count?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 28, 2022, 10:49pm UTC](https://discuss.elastic.co/t/mapping-explosion-vs-the-filebeat-template/295886/2 "2022-02-28T22:49:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.