# Using wildcards to speficy multiple indexes in Kibana, is it still not supported? **URL:** \ **Category:** Elasticsearch\ **Created:** [December 18, 2014, 11:24am UTC](https://discuss.elastic.co/t/using-wildcards-to-speficy-multiple-indexes-in-kibana-is-it-still-not-supported/21311 "2014-12-18T11:24:55Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Vagif\_Abilov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vagif_abilov/32/788_2.png) [@Vagif\_Abilov](https://discuss.elastic.co/u/Vagif_Abilov)\ **Post date:** [December 18, 2014, 11:24am UTC](https://discuss.elastic.co/t/using-wildcards-to-speficy-multiple-indexes-in-kibana-is-it-still-not-supported/21311/1 "2014-12-18T11:24:55Z")
We have groups of multiple indexes which names differ in a few characters, and we want to query all indexes belonging to the same group. I've found some old threads where it's explained that Kibana doesn't support wildcard in index names (except for date specifier) and there only way to specify such multiple indexes is just to list all of them explicitly in Kibana settings. But that's not flexible in our case. I wonder if Kibana supports or plan to support wildcards in index names. Thanks in advance Vagif Abilov -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/eb384bad-c0b4-4081-a87f-f3aa128d1a14%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/eb384bad-c0b4-4081-a87f-f3aa128d1a14%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![antoine\_girbal](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@antoine\_girbal](https://discuss.elastic.co/u/antoine_girbal)\ **Post date:** [December 19, 2014, 7:53pm UTC](https://discuss.elastic.co/t/using-wildcards-to-speficy-multiple-indexes-in-kibana-is-it-still-not-supported/21311/2 "2014-12-19T19:53:42Z")
Vagif, you should try out Kibana 4, with which you can define either wildcard based name (e.g. logstash-\*) or date based name (e.g. logstash-YYYY.MM.DD) Note that it is typically much more efficient to use a date based approach, since K4 can then only query the indices that match your query, instead of all of them. On Thursday, December 18, 2014 3:24:55 AM UTC-8, Vagif Abilov wrote: > We have groups of multiple indexes which names differ in a few characters, > and we want to query all indexes belonging to the same group. I've found > some old threads where it's explained that Kibana doesn't support wildcard > in index names (except for date specifier) and there only way to specify > such multiple indexes is just to list all of them explicitly in Kibana > settings. But that's not flexible in our case. > > I wonder if Kibana supports or plan to support wildcards in index names. > > Thanks in advance > > Vagif Abilov -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4d51b047-6d15-45d1-b411-361b03bebf41%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d51b047-6d15-45d1-b411-361b03bebf41%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:42am UTC](https://discuss.elastic.co/t/using-wildcards-to-speficy-multiple-indexes-in-kibana-is-it-still-not-supported/21311/3 "2017-07-06T00:42:38Z")