# Force filebeat index to use specific/correct type

**URL:** https://discuss.elastic.co/t/force-filebeat-index-to-use-specific-correct-type/164653
**Category:** Elasticsearch
**Created:** [January 17, 2019, 2:41pm UTC](https://discuss.elastic.co/t/force-filebeat-index-to-use-specific-correct-type/164653 "2019-01-17T14:41:46Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)
#### Post date: [January 17, 2019, 2:41pm UTC](https://discuss.elastic.co/t/force-filebeat-index-to-use-specific-correct-type/164653/1 "2019-01-17T14:41:46Z")

</div>

Im pulling in some stdout/stderr from kubernetes via filebeat. When the indexes are created both the numeric and string values are showing up in kibana with '?' for type.

Looking at the index via **GET /filebeat-\<date\>** I see that the string fields are marked as 'text' but so is the numeric field.

Why aren't the fields being recognized as the correct type and how do I fix this?

* * *

Edit - I get that I need to setup a template but given that it's using filebeat I didn't want to mess up any defaults.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 14, 2019, 2:41pm UTC](https://discuss.elastic.co/t/force-filebeat-index-to-use-specific-correct-type/164653/2 "2019-02-14T14:41:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.