-
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
[Log Explorer] Add link to fall back to Discover #165220
Comments
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
Looks like, when factoring out the DiscoverContainer, we lost the ability to customize the top nav menu entries, which affects this issue. I'll investigate the cause and open a new issue if necessary. |
Since we're our own app we can control the I'm not sure whether it'll work for serverless too, though. |
## 📓 Summary Closes #165220 This PR introduces a new fallback link from the Log Explorer application to Discover. To correctly retrieve the details required to correctly navigate to Discover with the used data view and filters, the LogExplorer component accepts now a new `state$` behaviour subject as a property that can be used to notify the consumers of any change from the internal state. https://github.com/elastic/kibana/assets/34506779/c8176ef2-7a3b-4c7e-860a-450ba677412a ## 🧪 Test suite ``` ↳ Observability Log Explorer ↳ Header menu ↳ should inject the app header menu on the top navbar ↳ Discover fallback link ↳ should render a button link ↳ should navigate to discover keeping the current columns/filters/query/time/data view ``` --------- Co-authored-by: Marco Antonio Ghiani <[email protected]> Co-authored-by: kibanamachine <[email protected]>
📓 Summary
Since the log explorer imposes restrictions on the indices that can be viewed, we want to offer a fall-back link, which allows the user to navigate to Discover, which doesn't have these restrictions nor the special affordances.
✔️ Acceptance criteria
🎨 Mock-ups
The text was updated successfully, but these errors were encountered: