Index patterns - comma-separated list

Elastic Stack Kibana
1

Hi

ELK 6.2.3 - In Kibana I can define an index pattern based on a comma-separated list of indexes, rather than using wildcards. Kibana appears to accept this and shows me the correct list of indexes matching pattern, when creating the pattern. Also shows the correct combined list of fields from all indexes in my list when I review the index pattern. However, when I try to use this index pattern for a search in Discover tab, no results.

Is this comma-separated list a valid way to create an index pattern, and if not, why does Kibana seem to accept it? Thanks!

Regards,

Adrian

2

hi @aidofitz,

interesting, I can reproduce this. Using comma-separation isn't documented usage in Kibana (https://www.elastic.co/guide/en/kibana/current/index-patterns.html), but it certainly does work in the indexpattern-creation wizard. It's also supported in ES of course.

e.g.

POST foobar1/type 
{
  "some": "value"
}

POST foobar2/type 
{
  "some other": "other value"
}


GET foobar1,foobar2/_search


GET foobar*/_search

My foobar* index pattern would display fine in Discover, but not my foobar1,foobar2 index pattern.

This is may be a bug. Could you log this inhttps://github.com/elastic/kibana/issues/new? thx!

3

Thanks. Done - https://github.com/elastic/kibana/issues/17748

4

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