[Discover] Add link from Index management

[kertal]

Summary

While preparing a presentation about linking to Discover I figured out it would be nice the provide a link from index management to Discover, so users could directly look at the documents of their indices. The link is visible in the flyout showing details about a index or data stream, and the button opens up the selected index / data stream as an ad-hoc data view in Discover. No data view persistence upfront is needed.

Kapture.2023-03-24.at.22.55.58.mp4

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[elasticmachine]

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

[alisonelizabeth]

This is a really cool feature. Thanks for working on this @kertal!

One thought I had is it might be better to display the link in the details panel, rather than the table. If a user has a lot of indices/data streams, it be a little overwhelming having the same icon for each row. Although the tradeoff is it's not as discoverable (no pun intended 😅 ).

I see the PR is still in draft. Was your expectation just to get initial thoughts on this feature?

[kertal]

This is a really cool feature. Thanks for working on this @kertal!

One thought I had is it might be better to display the link in the details panel, rather than the table. If a user has a lot of indices/data streams, it be a little overwhelming having the same icon for each row. Although the tradeoff is it's not as discoverable (no pun intended 😅 ).

Fine with that, I think having the possibility to link to the documents of the indices is what's important. we can integrate on that.

I see the PR is still in draft. Was your expectation just to get initial thoughts on this feature?

You know I started this to demonstrate how easy it is to link to Discover. Also it was always something I thought was missing, a list of indices needs a button to show the documents of the indices. So why did I not iterate on it? Lack of time. I will apply your suggestion, which is a pretty safe path for adding this.

[kertal]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 3ff2eb0

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
indexManagement	488	489	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
indexManagement	525.5KB	526.0KB	+587.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	433	436	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	513	516	+3

History

• 💚 Build #115466 succeeded 90217d8
• 💔 Build #115454 failed a5df69f
• 💔 Build #113407 failed a6b7115
• 💔 Build #113373 failed d5a3368
• 💔 Build #111872 failed 1dfa06e

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @kertal

[alisonelizabeth]

Thanks @kertal! Latest LGTM.

[jughosta]

Would it be possible to detect that an index pattern has a time field and show a histogram on Discover page? Or at least for data streams.

[kertal]

Would it be possible to detect that an index pattern has a time field and show a histogram on Discover page? Or at least for data streams.

We have something like this in Discover:

kibana/src/plugins/discover/public/application/main/services/discover_state.ts

Line 399 in 2d8a2b5

newDataView.timeFieldName = '@timestamp';

But it's just looking for the field @timestamp and if it is date ... We could do something like this here, or we create a follow up issue this improve and centralize this logic ... eg.

• Check if here is just a single date field ... use that
• Check if there are several date fields, look for timestamp, @timestamp, ...
• Check for ECS ...

WDYT? I do agree it would be convenient to have something like this, just thinking if we shouldn't aim higher for more improvement

[jughosta]

@kertal Sure, I agree with an iterative approach! I was only concerned that showing Discover page without time based sorting and histogram for time-based indices might appear unexpected/buggy for users. If it's not the case then LGTM 👍

[kertal]

@kertal Sure, I agree with an iterative approach! I was only concerned that showing Discover page without time based sorting and histogram for time-based indices might appear unexpected/buggy for users. If it's not the case then LGTM 👍

I do agree we should further improve this area and will open an issue for that, thx for you valuable input! 👍