# Too many field in metricbeat

**URL:** https://discuss.elastic.co/t/too-many-field-in-metricbeat/242572
**Category:** Beats
**Tags:** metricbeat
**Created:** [July 24, 2020, 10:07pm UTC](https://discuss.elastic.co/t/too-many-field-in-metricbeat/242572 "2020-07-24T22:07:45Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![tactics](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@tactics](https://discuss.elastic.co/u/tactics)
#### Post date: [July 27, 2020, 2:11pm UTC](https://discuss.elastic.co/t/too-many-field-in-metricbeat/242572/4 "2020-07-27T14:11:42Z")

</div>

@elasticforme - I have tried editing the fields.yml to remove the modules that aren't needed, this has reduced the number of fields in my index template. Still checking to see if there are any issues with this but this might work for you as well.

> [@Filebeat Index Template from Modules](https://discuss.elastic.co/t/filebeat-index-template-from-modules/242660):
>
> Hi, Not sure if I am overcomplicating things and bothering unnecessarily... I have finally got apache logs importing nicely using Filebeat and the Apache module. I am simply using the fields.yml and therefore the index template is massive... Is there any way to only include the fields that are used in the module or maybe use the Index to generate fields and mappings that are being used? Maybe I don't actually need to worry about this as the field definitions and mappings don't take up space…

---

_[View the full topic](https://discuss.elastic.co/t/too-many-field-in-metricbeat/242572)._