kibana icon indicating copy to clipboard operation
kibana copied to clipboard

Index Pattern should be inferred from the time range when applicable

Open omrikurtz opened this issue 3 years ago • 3 comments

What: We'd like to be able to infer the index pattern needed for a visualization from the time range that it queries, when applicable. Examples: if the time range filters for the last 24 hours, the index pattern should be: logs-2022-06. If the time range filters for 3 months, it would be logs-2022-06,logs-2022-05,logs-2022-04.

Why: I believe having such a feature would improve performance (and cluster stability) for many organizations which rely on Kibana as an easy-to-use tool for accessing data and creating visualizations quickly. The time-range field is many times the same field that is used to separate the data to different indexes, so I see this as a feature that many users would benefit from.

I'll add that we have many Kibana users in our org, and some of them are less technical than others. Sometimes they used the wrong index-pattern for their visualizations, which may result in one of two undesirable scenarios:

  1. Performance/cluster stability impact (in the case of querying too many indices)
  2. Incomplete picture of the data (in case of not querying all the relevant data)

Please let me know if such a feature/roadmap exists, as this would be a life saver for us :)

omrikurtz avatar Jun 30 '22 14:06 omrikurtz

+1 would be very much useful!

Elly-Mandliel-Forter avatar Jun 30 '22 14:06 Elly-Mandliel-Forter

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

elasticmachine avatar Jun 30 '22 14:06 elasticmachine

Elasticsearch is quite efficient when it comes to filtering out shards that do not have any data within a time range, so I would recommend testing to see what the difference is for your specific scenario as it may vary depending on data and number of indices and shards.

Please let me know if such a feature/roadmap exists, as this would be a life saver for us :)

It sounds like you could use some performance analysis.

mattkime avatar Jun 30 '22 15:06 mattkime

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

ppisljar avatar Aug 11 '22 11:08 ppisljar