# Convert to non-time-interval based index pattern

**URL:** <https://discuss.elastic.co/t/convert-to-non-time-interval-based-index-pattern/146478>\
**Category:** Kibana\
**Created:** [August 29, 2018, 7:32am UTC](https://discuss.elastic.co/t/convert-to-non-time-interval-based-index-pattern/146478 "2018-08-29T07:32:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![xenoid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xenoid/32/20672_2.png) [@xenoid](https://discuss.elastic.co/u/xenoid)\
**Post date:** [August 29, 2018, 7:32am UTC](https://discuss.elastic.co/t/convert-to-non-time-interval-based-index-pattern/146478/1 "2018-08-29T07:32:19Z")

</div>

Hello Kibana community,

today I came across a problem in my ES-test-cluster.  
I've got a few nodes running on version 2.4.0 equipped with Kibana 4.6.6.  
In order to upgrade this cluster though, I need to convert the time-interval based index pattern to a non time-interval based one as this is deprecated in later versions of Kibana.  
I have got hundreds of objects referencing the time-interval based index pattern, so to manually update these would be a pain. 😓

So, is there any recommended way to update my objects to a new index pattern?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 29, 2018, 8:14am UTC](https://discuss.elastic.co/t/convert-to-non-time-interval-based-index-pattern/146478/2 "2018-08-29T08:14:44Z")

</div>

> [@xenoid](#):
>
> In order to upgrade this cluster though, I need to convert the time-interval based index pattern to a non time-interval based one as this is deprecated in later versions of Kibana.

Why? You can still use time-based indices in later versions, e.g. `logstash-2018.08.26`. It is just that Kibana no longer relies on the index name to determine which indices to query. In version 5.x Kibana uses the field stats API if I recall correctly, and more recently querying all indices has been made much more efficient in Elasticsearch, so Kibana no longer needs to do these extra steps.

---

<div class="post-metadata">

**Author:** ![xenoid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xenoid/32/20672_2.png) [@xenoid](https://discuss.elastic.co/u/xenoid)\
**Post date:** [August 29, 2018, 8:47am UTC](https://discuss.elastic.co/t/convert-to-non-time-interval-based-index-pattern/146478/3 "2018-08-29T08:47:53Z")

</div>

Ok, I knew that but using an index pattern like `[logstash-]YYYY.MM.DD` is possible and wont cause any problems? By using `logstash-*` objects can't find their original pattern.

You see, Kibana 4 wont let me configure the pattern unless I use a wildcard.

 ![dragon_2018-08-29_10-49-39](https://us1.discourse-cdn.com/elastic/original/3X/a/f/af234c46c1aac719025d1e660ade8a3b7c1254af.png)

---

<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:** [September 26, 2018, 8:47am UTC](https://discuss.elastic.co/t/convert-to-non-time-interval-based-index-pattern/146478/4 "2018-09-26T08:47:54Z")

</div>

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