[Proposal] - Improve Discover Look and Feel #6067
Assignees
Labels
Comments
7 tasks
kavilla
added a commit
to kavilla/OpenSearch-Dashboards-1
that referenced
this issue
Jun 12, 2024
Adds new query editor in replacement of query string input. Utilizing: ``` data.enhancements.enabled: true ``` And enabling the Advanced Setting: `query:enhancements:enabled` Also, cleans up the toggling since it is now two different components. Related issue: opensearch-project#6067 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
kavilla
added a commit
to kavilla/OpenSearch-Dashboards-1
that referenced
this issue
Jun 12, 2024
Adds new query editor in replacement of query string input. Utilizing: ``` data.enhancements.enabled: true ``` And enabling the Advanced Setting: `query:enhancements:enabled` Also, cleans up the toggling since it is now two different components. Related issue: opensearch-project#6067 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
kavilla
added a commit
that referenced
this issue
Jun 14, 2024
* [Discover-next] query editor and UI settings toggle Adds new query editor in replacement of query string input. Utilizing: ``` data.enhancements.enabled: true ``` And enabling the Advanced Setting: `query:enhancements:enabled` Also, cleans up the toggling since it is now two different components. Related issue: #6067 Signed-off-by: Kawika Avilla <kavilla414@gmail.com> * Remove commented out code Signed-off-by: Kawika Avilla <kavilla414@gmail.com> --------- Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
opensearch-trigger-bot bot
pushed a commit
that referenced
this issue
Jun 14, 2024
* [Discover-next] query editor and UI settings toggle Adds new query editor in replacement of query string input. Utilizing: ``` data.enhancements.enabled: true ``` And enabling the Advanced Setting: `query:enhancements:enabled` Also, cleans up the toggling since it is now two different components. Related issue: #6067 Signed-off-by: Kawika Avilla <kavilla414@gmail.com> * Remove commented out code Signed-off-by: Kawika Avilla <kavilla414@gmail.com> --------- Signed-off-by: Kawika Avilla <kavilla414@gmail.com> (cherry picked from commit a4aa682) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
kavilla
pushed a commit
that referenced
this issue
Jun 20, 2024
* [Discover-next] query editor and UI settings toggle Adds new query editor in replacement of query string input. Utilizing: ``` data.enhancements.enabled: true ``` And enabling the Advanced Setting: `query:enhancements:enabled` Also, cleans up the toggling since it is now two different components. Related issue: #6067 * Remove commented out code --------- (cherry picked from commit a4aa682) Signed-off-by: Kawika Avilla <kavilla414@gmail.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
The following proposal illustrates an improved look and feel for Discover that provides users with a compact, simplified and
functional interface to explore their data.
User Interface simplification
Through user research we uncovered that users prefer a more compact UI that showcases more information without being overwhelming. Through spacing and layout improvements the UI was simplified and made to house more data. Users are able to adapt the interface based on their needs and preferences based on controls for specific elements.
User controls
Users have controls over the interface and are able to collapse the side panel, histogram, and query bar to free up space for exploration as needed by their workflows and preferences. Additional controls have been made available like the ability to control the density of events in the table.
User.controls.2.mp4
Table Density Controls
Users are able to control the density of events shown in the results table based on their needs and workflow.
Collapsed view
Users are able to collapse elements to create space based on their use cases and needs
The text was updated successfully, but these errors were encountered: