kibana连接elasticsearch的索引统一管理

[HFNU112]

Describe the feature:
一个project,如果按照类型划分有多个索引，现存的索引管理这方面不能管理多个索引，一次性查询不好管理，不如放到类似一个目录下（树形结构）那样进行管理。另外在现有功能上丰富下增删查改。现有的索引模板虽然可以相同索引名的前缀的相关，但是对于一次查询多个索引管理上不太友好。当然kibana本身提供的UI界面在操作elasticsearch的脚本语句上还是很方面，有助于新手快速熟悉新的脚本语法，这款产品在项目中受到欢迎。在项目中数据收集、分析速度挺快的相比于数据库。如果我提到的issue可以完善，这款产品更有利开发者的使用体验。
Describe a specific use case for the feature:

[jsanz]

Pasting the google translation of the issue title and body

Kibana connects to elasticsearch for unified index management

If a project has multiple indexes divided by type, the existing index management cannot manage multiple indexes, and it is difficult to manage one-time queries. It is better to manage them in a directory (tree structure). In addition, the existing functions are enriched and added, deleted, checked and modified. Although the existing index template can be related to the prefix of the same index name, it is not very friendly for querying multiple indexes at one time. Of course, the UI interface provided by kibana itself is still very convenient for operating elasticsearch script statements, which helps novices quickly become familiar with the new script syntax. This product is welcomed in the project. In the project, data collection and analysis are very fast compared to databases. If the issue I mentioned can be improved, this product will be more beneficial to developers' experience.

@HFNU112, thanks for submitting. I'm failing to understand what is the feature request here. Elasticsearch can target multiple indices based on a pattern, as described here. Kibana leverages this feature on Data Views, allowing to add more logic to that (field formatters, default time field).

Can you provide (in English, please) a more detailed description of your request? If your request is more related to Elasticsearch, I can migrate the issue to that repository.

Thanks!

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[HFNU112]

kibana connects to the es directory tree structured management index library

Different business types of the project: login, user, order. Established index library index_login, index_user, index_order. I now want to document the contents of these indexes once and for all via a DSL script, while visualizing them in kibana
index_root
| ___
index_login
|___
index_user

This tree structure manages index libraries managed by different business types under the same project. At present, using kibana operation elastissearch7 to create the index pattern that needs to be matched in the index template, it is really convenient to count the number of documents in the index library created by the index pattern under the index template. This product has better performance in DSL script query compared to database. For a novice who is not familiar with the syntax of the DSL query, the syntax error when editing the DSL script is relatively friendly. If you can enrich the problems I described, then this product is more popular with developers!

@jsanz

[jsanz]

Hi, thanks for creating an issue, but this is something you want to discuss in our discussion forum at:

https://discuss.elastic.co/

Closing