-
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
[Dataset quality] Add actions column #170236
Comments
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
@yngrdyn Do we still need the view in dashboard aciton? I guess for first phase we need to filter the actions as per the last design meeting? |
We are in the process of update the tickets to match the last designs |
@yngrdyn for the scope of this ticket do we only display the Open link in the actions column? |
that's correct, it will be the only action for now. We can start building more actions in the future |
Closes #170236. ### Changes This PR focuses on adding an action per dataset + namespace to navigate to Observability log explorer. At the same time I took the opportunity to update `Open in discover` link to include the controls present in `Observability Log Explorer` state (atm just `namespace`) 1. Extracted `getRouterLinkProps` to a new package for reusability. 2. New `Actions` column was added to table. 3. `LogExplorerLink ` component was introduced, to reuse the navigation logic between the table and the flyout. 4. `getDiscoverFiltersFromState` was added to combine state filters and controls into discover state when navigating to discover #### Demo https://github.com/elastic/kibana/assets/1313018/a3f38615-d8ae-432b-ba7b-05a6901f870c --------- Co-authored-by: kibanamachine <[email protected]>
📓 Summary
Allow users to navigate to Log explorer.
✔️ Acceptance criteria
Actions
.Integration
>Dataset
>namespace
selected.The text was updated successfully, but these errors were encountered: