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

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"
}
}
}
}

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.

ok thanks for the info

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