Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Explorer - Revamping Discover to be able to be used for all of OpenSearch Dashboards data exploration use cases #3056

Open
elfisher opened this issue Dec 9, 2022 · 6 comments
Assignees
Labels
de-angular de-angularize work discover for discover reinvent enhancement New feature or request needs more info Requires more information from poster needs research

Comments

@elfisher
Copy link

elfisher commented Dec 9, 2022

This is a place holder for a proposal to revamp Discover so that it can be used in all of our experiences that require data exploration rather than having separate document exploration user experiences. For example today Event Explorer and Discover have similar functionality and are used for similar use cases. This proposal is to revamp discover to work across all these use cases.

Proposal: Create a new plugin with the following components...
image

@elfisher elfisher added the enhancement New feature or request label Dec 9, 2022
@elfisher elfisher self-assigned this Dec 9, 2022
@joshuarrrr joshuarrrr added the discover for discover reinvent label Dec 9, 2022
@joshuarrrr
Copy link
Member

For example today Event Explorer and Discover have similar functionality and are used for similar use cases.

I know this is just a placeholder, but it's absolutely critical that we're able to actually articulate the current use cases of Discover and Event Explorer, as well as specific features/functionality, before we can assess where the overlaps and gaps are and choose a technical approach.

How is this issue distinct from #1792? Should we update #1792 to be an RFC that asks for specific use cases or pain points from the community?

@joshuarrrr
Copy link
Member

I've also tagged discover-related bugs and feature requests with the discover for discover reinvent label, so that it's easier to track existing known issues.

@elfisher
Copy link
Author

elfisher commented Dec 14, 2022

@joshuarrrr you are right. This is duplicative/similar to #1792.

@ananzh
Copy link
Member

ananzh commented Dec 20, 2022

Add two draft Issues in #1792 (here) and also update the same contents below

@BSFishy BSFishy added needs research needs more info Requires more information from poster labels Jan 26, 2023
@BSFishy
Copy link
Contributor

BSFishy commented Jan 26, 2023

@ahopp to provide guidance when the working backwards doc for Discover 2.0 is completed

@seanneumann seanneumann pinned this issue Mar 5, 2023
@seanneumann seanneumann changed the title Discover 2.0 - Revamping Discover to be able to be used for all of OpenSearch Dashboards data exploration use cases Data Explorer - Revamping Discover to be able to be used for all of OpenSearch Dashboards data exploration use cases Mar 5, 2023
@ashwin-pc ashwin-pc added the de-angular de-angularize work label May 11, 2023
@seanneumann seanneumann unpinned this issue May 18, 2023
@ashwin-pc
Copy link
Member

Proposal for Data Explorer/Discover 2.0 outlined in #4165

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
de-angular de-angularize work discover for discover reinvent enhancement New feature or request needs more info Requires more information from poster needs research
Projects
Status: Upcoming release (TBD)
Development

No branches or pull requests

6 participants