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

[Meta] Unified search experience across kibana #126095

Closed
6 of 18 tasks
stratoula opened this issue Feb 21, 2022 · 7 comments
Closed
6 of 18 tasks

[Meta] Unified search experience across kibana #126095

stratoula opened this issue Feb 21, 2022 · 7 comments
Labels
Feature:Unified search Unified search related tasks impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Meta Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@stratoula
Copy link
Contributor

stratoula commented Feb 21, 2022

Describe the feature:
We want to unify the search experience across Elastic with a composable and extensible query bar.

Problem statements (high level)

  • Inconsistent: Why doesn’t it work like Discover in Solutions?
  • This OR that: It’s hard to setup boolean expressions around my complex filters and understand the relationship between filters and the query bar. Security team solving for this today
  • So much interface: the query bar takes up two full rows before the content can start and the top of Kibana looks busy. Solution teams have been working to solve this which has lead to inconsistency
  • Not in my language: Rather than using a configuration UI with fields I’d like to query using ES|QL / EQL (a tier 3 security analyst), SQL (an analyst/manager), or eventually PromQL (a SRE)
  • Order matters: The information hierarchy is not predictable in pages that have a data view context (like Discover and Lens)

Capabilities:

  • Support text-based (non-UI based) languages.
  • Different search languages (DSL, SQL, EQL, PromQL)
  • Enhanced filtering experience on top of any search
  • Expand filter capabilities to including ORs
  • Extensible to support advanced queries

This is a big project that will be implemented on various phases

Phase 1: Redesign of the current search experience

In this phase we are not going to offer more features to our users. We are just going to change the UI and improve the current experience.

Tasks:

  • Search bar is bigger
  • Combine Filter menu, Language switcher and Saved Queries menu into one
  • Move Data Views selector to top bar
  • Move the add filter capability to right of the search bar

Phase 2: Adapt text-based languages

Phase 3: Users can apply more than one saved search

Phase 4: Add complex filter capabilities (ORs)

Phase 5: Eliminate the filter pills (references)

Adoption

(this list is incomplete, please fill in missing items or remove ones that will not be using Unified Search)

Observability


Open Discussions

  • What are we going to do with the pinned filters functionality?
@stratoula stratoula added Meta Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas Team:Visualizations Visualization editors, elastic-charts and infrastructure Team:AppServicesSv Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. labels Feb 21, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesUx)

@ThomThomson
Copy link
Contributor

Removing the Presentation team label from this as it doesn't seem like there is any work required from our side at the moment.

@ThomThomson ThomThomson removed the Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas label Apr 5, 2023
@stratoula stratoula added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Jun 2, 2023
@davismcphee davismcphee added the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 8, 2023
@stratoula
Copy link
Contributor Author

We are not tracking this anymore, I am closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Unified search Unified search related tasks impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Meta Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

4 participants