# Remove exotic modules fields from filebeat template

**URL:** https://discuss.elastic.co/t/remove-exotic-modules-fields-from-filebeat-template/362551
**Category:** Beats
**Tags:** docker, filebeat
**Created:** [July 4, 2024, 12:51pm UTC](https://discuss.elastic.co/t/remove-exotic-modules-fields-from-filebeat-template/362551 "2024-07-04T12:51:48Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)
#### Post date: [July 4, 2024, 12:51pm UTC](https://discuss.elastic.co/t/remove-exotic-modules-fields-from-filebeat-template/362551/1 "2024-07-04T12:51:48Z")

</div>

When filebeat runs, it creates an index template "filebeat-8.14.1" with a ton of mapping fields:

"kafka", "santa" etc....

This is fine but when an user creates a dashboard, he sees all these fields and lost time to find the right field.

 ![Capture d’écran, le 2024-07-04 à 08.50.58](https://us1.discourse-cdn.com/elastic/original/3X/5/1/5176257b1b5e31c3079c42d81405c6a5aeee19c4.png)

**How can we disable fields from unused modules (maybe a simple cli flag, or a stage in custom Docker image) ?**