Skip to content

Commit

Permalink
address vale errors
Browse files Browse the repository at this point in the history
Signed-off-by: Lu Yu <[email protected]>
  • Loading branch information
BionIT committed May 15, 2024
1 parent ca9e248 commit 075a1f1
Showing 1 changed file with 11 additions and 11 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -12,17 +12,17 @@ meta_description: This blog provides a quick glance at the accumulated features

Before 2.4 release, OpenSearch Dashboards only works with a single OpenSearch cluster, and it is impossible to view data from different clusters within the dashboards.

In 2.4, multiple data source feature was introduced together with data source management UI portal to allow users to add new data source to the dashboards, create index patterns based on those data sources, and execute queries against a specific connected data source. In 2.6 release, AWS signature Version 4 was added as one authentication type supported by multi data source in addition to basic auth. Onwards, multi data source support at core plugin including dev tools was added in 2.7 release, sample data support was added in 2.9 release, then added in for Vega visualization in 2.13. File based saved objects import sourced from multi data source was added into OpenSearch Dashboards in 2.12.
In 2.4, multiple data source feature was introduced together with data source management UI portal to allow users to add new data source to the dashboards, create index patterns based on those data sources, and execute queries against a specific connected data source. In 2.6 release, AWS signature Version 4 was added as one authentication type supported by multi data source in addition to basic auth. Thereafter, multi data source support at core plugin including `Dev Tools` was added in 2.7 release, sample data support was added in 2.9 release, then added in for Vega visualization in 2.13. File based saved objects import sourced from multi data source was added into OpenSearch Dashboards in 2.12.

In this release, to ensure users that have been using the multiple data source feature to have a consistent experience in the dashboards, we enabled multiple data source at 8 OpenSearch Dashboards plugins including index management, machine learning, search relevance, anomaly detection, maps, security, notification, etc, and enabled multiple data source at 2 core plugins including TSVB and Region Map. In addition, we introduced default data source feature which will be the default option chosen for all plugins pages that support multi data source.
In this release, to ensure users that have been using the multiple data source feature to have a consistent experience in the dashboards, we enabled multiple data source at 9 OpenSearch Dashboards plugins including index management, machine learning, search relevance, anomaly detection, maps, security, notification, query workbench, trace analytics, and enabled multiple data source at 2 core plugins including TSVB and Region Map. In addition, we introduced default data source feature which will be the default option chosen for all plugins pages that support multi data source.

This blog provides a quick glance at the accumulated features of multi-data sources from version 2.4 to 2.14 and how these features empower your productivity with unified experience.

## User scenario - Single panel of glass of data
Use one OpenSearch Dashboards to present data from multiple OpenSearch Cluster

### Case 1
In large corporation, user’s data has been distributed in different datasource, before multiple datasource was introduced. User has to put data into centralized storage before they could analyze it. With the build-in support of multiple datasource, OpenSearch dashboards could present data from multiple data sources within a single dashboard. Starting 2.14, we support additional visualization type including Vega, TSVB, Region Map, in addition to index pattern based visualizations.
In large corporation, user’s data has been distributed in different data sources, before multiple data source was introduced. User has to put data into centralized storage before they could analyze it. With the build-in support of multiple data source, OpenSearch dashboards could present data from multiple data sources within a single dashboard. Starting 2.14, we support additional visualization type including Vega, TSVB, Region Map, in addition to index pattern based visualizations.
<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/dashboards_overall.png"/>

### Case 2
Expand All @@ -35,17 +35,17 @@ Also, the referenced data sources from the current map layers are indicated by c
## User scenario - Centralized Data Management and Governance
Use one OpenSearch Dashboards as admin tool to manage resource on multiple OpenSearch Cluster

### Case 1 Manage indices, streams, aliases, in a centralized place
### Case 1 Manage indexes, streams, aliases, in a centralized place
Before 2.14, index management within the dashboards allows to perform management operations on indexes within one OpenSearch cluster. With multi data source support added for the plugin in 2.14, all operations include create, read, update, delete (CRUD), mapping operations for indexes, index templates, and aliases living in different data sources can be completed in one dashboard. Using indexes as an example, indexes from different data sources can be displayed by switching source at the top navigation bar, and operations can be done by selecting a specific index then choose the desired option.
<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/indexes_overview.png"/>

Detailed information about the selected index can be viewed by clicking on the index name.
<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/detailed_index.png"/>

Note that id of the data source which is UUID is embedded into the url, thus specific page can be bookmarked and shared.
Note that id of the data source is set as query parameter into the dashboard endpoint, thus specific page can be bookmarked and shared.

### Case 2 Manage roles, internal users at one central place
Together with 2.14 release, dashboards security plugin has enabled multi data source support allowing admin users to manage roles and internal users from different data sources in one central place. Use roles as example, existing role from selected data source is displayed.
Together with 2.14 release, dashboards Security plugin has enabled multi data source support allowing admin users to manage roles and internal users from different data sources in one central place. Use roles as example, existing role from selected data source is displayed.

<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/roles_overview.png"/>

Expand All @@ -66,10 +66,10 @@ Starting 2.14 , machine learning plugin enabled multi data source support, and b

<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/models_overview.png"/>

Also note that the pre-trained models were deployed to the selected cluster via developer tools page.
Also note that the pre-trained models were deployed to the selected cluster using `Dev Tools` page.

### Case 5 use dev tools to query/modify data via API against specific data source at one place
Starting 2.7, dev tool is integrated with multi data source, and by selecting the target data source to execute the command on, users can query/modify the backend data directly at one central place.
### Case 5 use `Dev Tools` to query/modify data using API against specific data source at one place
Starting 2.7, `Dev Tools` is integrated with multi data source, and by selecting the target data source to execute the command on, users can query/modify the backend data directly at one central place.

<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/devtool.png"/>

Expand All @@ -91,12 +91,12 @@ Detectors can be created, viewed, and modified in one dashboard.
<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/detector_detail.png"/>

### Case 3 Compare query results from different data sources
Before 2.14, dashboards only allow comparison of search results from indices within one cluster. Starting 2.14, Search relevance plugin enabled multi data source support, and we can compare the search results from indices within 2 different clusters. Note that the data source selector within the page pre-populates the available data sources to choose from.
Before 2.14, dashboards only allow comparison of search results from indexes within one cluster. Starting 2.14, Search relevance plugin enabled multi data source support, and we can compare the search results from indexes within 2 different clusters. Note that the data source selector within the page pre-populates the available data sources to choose from.

<img src="/assets/media/blog-images/2024-04-30-embrace-multiple-data-source-in-opensearch-dashboards/compare_queries.png"/>

## Summary
OpenSearch Dashboards provides direct visualization interface of user’s data located in the OpenSearch cluster, with multiple data source feature, OpenSearch Dashboards serves as the one dashboard for all connected OpenSearch clusters, allowing to find the right information, analyze log data, build report, etc.
OpenSearch Dashboards provides direct visualization interface of user’s data located in the OpenSearch cluster, with multiple data source feature, OpenSearch Dashboards serves as the one dashboard for all connected OpenSearch clusters, allowing to find the right information, analyze log data, build report, and many more.

Special thanks to Ramakrishna Chilaka, Prabhat Sharma, Derek Ho, Junqiu Lei, Jackie Han, Riya Saxena, Sumukh Hanumantha Swamy, Lin Wang, Ella Zhu, Emma Jin, Huy Nguyen, Zhongnan Su for their work to enable multi data source support in the OpenSearch Dashboards and plugins!

Expand Down

0 comments on commit 075a1f1

Please sign in to comment.