[Dataset quality] Link to dataset health page from Observability Logs Explorer

[yngrdyn]

📓 Summary

Allow users to navigate to the page.

• 🎨 Figma: https://www.figma.com/file/aaJNMsOklYhjwtu5TP7UDK/%5BLogs%2B%5D-Organize-and-Admin?node-id=2106%3A381912&mode=dev

✔️ Acceptance criteria

• A link is added to Observability Log Explorer
  • User is redirected to dataset health page when clicking the link
• Breadcrumbs reflect the path the user took to get to the page
  • stateful: Observability > Logs > Explorer > Datasets
  • serverless: Log Explorer > Datasets

💡 Implementation hints

• The link should be placed in x-pack/plugins/observability_log_explorer/public/components/log_explorer_top_nav_menu.tsx.

[elasticmachine]

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

[mohamedhamed-ahmed]

Got a couple of questions here:

1. Are we planning to implement this using locators (probably)
2. Do we need to carry over any filtrations or params from the log explorer?

[yngrdyn]

1. Are we planning to implement this using locators (probably)

I think we should

2. Do we need to carry over any filtrations or params from the log explorer?

This is a good question, not sure about this one. For example if a user has selected a dataset inside an integration and we navigate to dataset quality using those values (through filters) they might not understand, quickly, that they can see all of their datasets there. What are your thoughts here @isaclfreire and @ruflin?

[isaclfreire]

I would separate the dataset health page behaviour to any filtering applied earlier on Logs Explorer. The page itself has already a dedicated search and filtering that has different parameters

[mohamedhamed-ahmed]

@isaclfreire I see your point. I was just thinking that lets say for example the user is on Logs Explorer with multiple datasets selected and a specific timeframe. The user then clicks on the dataset quality link, would it be best in terms of user experience to move the user's filters along to the quality page ( time filters and dataset selections) or isolate both pages.

[isaclfreire]

@mohamedhamed-ahmed I see your point, but I still believe both are isolated cases. I challenge the assumption that they would expect any correlation between an interactive component (data selector from search bar +/or query data picker) that shows results in the same page (data grid), and a static link in the sub-header. Both serve different objectives and purposes.

If we think users might want/need to check the health of an aggregation of datasets, based or not on a certain timeframe, it's best if we study a dedicated solution that makes the context a bit clearer.

[mohamedhamed-ahmed]

@isaclfreire Sounds good to me 👍 Thanks for your input :)