# Convert a string field to number, but only brand new indices recognized

**URL:** <https://discuss.elastic.co/t/convert-a-string-field-to-number-but-only-brand-new-indices-recognized/327512>\
**Category:** Logstash\
**Created:** [March 13, 2023, 3:39am UTC](https://discuss.elastic.co/t/convert-a-string-field-to-number-but-only-brand-new-indices-recognized/327512 "2023-03-13T03:39:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![KeithTt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keithtt/32/29447_2.png) [@KeithTt](https://discuss.elastic.co/u/KeithTt)\
**Post date:** [March 13, 2023, 3:39am UTC](https://discuss.elastic.co/t/convert-a-string-field-to-number-but-only-brand-new-indices-recognized/327512/1 "2023-03-13T03:39:55Z")

</div>

Logstash version: 6.3.0

Here is my config:

```auto
mutate {
    convert => { "bytes_sent" => "integer" }
}

```

I find that a indice which first created can recognized the config, but the others ones can not, even they created erveryday with different date suffix.

For example, there are some indices with same prefix like:

```auto
logstash-nginx-log-tfserving-2023.03.11
logstash-nginx-log-tfserving-2023.03.12
logstash-nginx-log-tfserving-2023.03.13

```

I guess I should delete all the indices with the same prefix to make the convert config recognized?

---

<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:** [April 10, 2023, 3:39am UTC](https://discuss.elastic.co/t/convert-a-string-field-to-number-but-only-brand-new-indices-recognized/327512/2 "2023-04-10T03:39:59Z")

</div>

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