# What is the limitation number to define the index names while creating the template

**URL:** https://discuss.elastic.co/t/what-is-the-limitation-number-to-define-the-index-names-while-creating-the-template/200979
**Category:** Elasticsearch
**Created:** [September 25, 2019, 7:33am UTC](https://discuss.elastic.co/t/what-is-the-limitation-number-to-define-the-index-names-while-creating-the-template/200979 "2019-09-25T07:33:12Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![satyam2593](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@satyam2593](https://discuss.elastic.co/u/satyam2593)
#### Post date: [September 25, 2019, 7:33am UTC](https://discuss.elastic.co/t/what-is-the-limitation-number-to-define-the-index-names-while-creating-the-template/200979/1 "2019-09-25T07:33:13Z")

</div>

I have scenario where i want to include the 10 different indices for the same template.  
Is it recommendable to do so, if not how can we approach this kind of scenario.  
How the order will work in the template?

Below is the sample template and indices

Template:  
PUT \_template/heap\_usage  
{  
"index\_patterns": [  
"heap\_usage\*",  
"talend\_dev1\_heap\_usage\*",  
"talend\_dev2\_heap\_usage\*",  
"talend\_dev3\_heap\_usage\*",  
"talend\_dev4\_heap\_usage\*"  
"talend\_preprod1\_heap\_usage\*",  
"talend\_preprod2\_heap\_usage\*",  
"talend\_preprod3\_heap\_usage\*",  
"talend\_preprod4\_heap\_usage\*",  
"talend\_prod1\_heap\_usage\*",  
"talend\_prod2\_heap\_usage\*",  
"talend\_prod3\_heap\_usage\*",  
"talend\_prod4\_heap\_usage\*",  
],  
"order": 10,  
"mappings": {  
"properties": {  
"path": {  
"type": "keyword"  
},  
"@timestamp": {  
"type": "date"  
},  
"log\_level": {  
"type": "keyword"  
},  
"message": {  
"type": "text"  
},  
"heap\_usage": {  
"type": "half\_float"  
},  
"@version": {  
"type": "keyword"  
}  
}  
}  
}

---

<div class="post-metadata">

### Author: ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [September 25, 2019, 11:51am UTC](https://discuss.elastic.co/t/what-is-the-limitation-number-to-define-the-index-names-while-creating-the-template/200979/2 "2019-09-25T11:51:18Z")

</div>

there is no limit on the index patterns. If this solves your use-case it is fine to go ahead. Keep in mind, that this will only be checked and parsed on index creation time, but not on index and query time, if that's something you are afraid of in terms of performance.

---

<div class="post-metadata">

### Author: ![satyam2593](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@satyam2593](https://discuss.elastic.co/u/satyam2593)
#### Post date: [September 25, 2019, 2:41pm UTC](https://discuss.elastic.co/t/what-is-the-limitation-number-to-define-the-index-names-while-creating-the-template/200979/3 "2019-09-25T14:41:45Z")

</div>

ok thanks for the info

---

<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: [October 23, 2019, 2:46pm UTC](https://discuss.elastic.co/t/what-is-the-limitation-number-to-define-the-index-names-while-creating-the-template/200979/4 "2019-10-23T14:46:25Z")

</div>

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