-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[GS] Entity results provider #74283
Comments
Pinging @elastic/kibana-platform (Team:Platform) |
Pinging @elastic/kibana-core-ui (Team:Core UI) |
+1 here from Observability. We'd like to dynamically define navigational entities based, for instance, on APM services, saved views in Metrics, etc.. Each part of our product may have additional requirements. |
Since the search framework already supports this today, I wonder if it'd be better if we closed this issue and delegated this to individual solution teams for further research. I'm not sure the Core team has enough knowledge about how other entities should be surfaced the user via the global search. We may need to provide additional customization options for how these results are displayed in the search framework, but I think the actual provider would be better implemented by the solutions themselves. |
+1, works for me Josh. I had opened this as a placeholder to future work (quite broadly, clearly). I think you're correct that the individual solution teams should be driving this and if you've prefer to close this issue vs. tracking the broader need, that works for me. |
Related to #72680, I can see the feature results evolving into more specific navigation requirements. For example, rather than returning
Cases
as a feature of theSecurity
app, it would be equally if not more beneficial to return cases that match an actual title. The same could be said about a timeline during investigation, a host in the metrics product, an index in index management, a monitor in uptime, a specific alert details page, etc. Being able to search for an entity and navigate to the most relevant view within a feature or application will ultimately streamline navigation.I've logged this issue separately from the saved objects results provider because I do not believe all of the examples I listed above have saved objects associated with them. I plan to do more research here and fine tune a list of solution / application entities that are separate from saved objects. Stay tuned 😎
The text was updated successfully, but these errors were encountered: