JacobBrandt
commented
3 years ago Could you elaborate on the different challenges you are saying exist with the current approach? You mentioned the cluster health but if the OpenSearch cluster heatlh is problematic then the user is going to have more problems then trying to get the saved objects to display on the tool.
As an aside, it's not immediately apparent if you are talking about Dashboards (a saved object within the tool) or OpenSearch Dashboards (this tool). I think there was a discussion in the forum and most agreed to not shorten/abbreviate terms especially when they can have several meanings. I'd love a different name for this tool as I see this becoming confusing in the long run.
seraphjiang
Is your feature request related to a problem? Please describe. Currently, Dashboards stores its metadata inside OpenSearch, though it works out of the box but it creates different challenges at scale for Dashboards to be operated and depending on the OpenSearch cluster health and could become unavailable. Idea to allow additional datasource to be configured for the metadata such as (kibana index) other than OpenSearch.
A clear and concise description of what the problem is.
Describe the solution you'd like Decouple the storage layer and create interfaces which will allow other datasource to be injected, start with sqllite for POC, once we have capability to add more we should add more such as RDBMS / NOSQL. It should be as light weight as possible.