Data stream selection in index pattern management

[mattkime]

Modify the following views to support data streams, index aliases, and frozen indices.

A new Es endpoint is being developed so the info can be gathered in a single request.

The define index pattern currently only shows matched indices. It will now show data streams index aliases. Frozen indices will be shown as well for users with the advanced setting search:includeFrozen enabled. Entities will be labeled with Eui Badges https://elastic.github.io/eui/#/display/badge

The timestamp selection step may be skipped if one or more data streams are selected and their timestamp fields are in agreement.

• Query new endpoint and display results.
• Support wildcards that match both data streams and indices for users transitioning to data streams.
• User will not be asked for timestamp field if matching a data stream (and only a data stream, or data streams with matching time fields)
• Support selection of frozen indices

Ticket for frozen index support - #61368

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[cjcenizal]

We could potentially display a data stream tag next to data stream related indices.

Is this part of the plan for implementing this issue @mattkime?

Also, do you think it would make sense to have a legend or some other explanation to explain data streams in this UI? For example, if a user selects data stream indices or a data stream index alias, can we surface a callout or maybe some info on a "review" step of the wizard to explain the relationship between index pattern, data stream, and indices? We could also add a link to the data stream docs.

[mattkime]

Is this part of the plan for implementing this issue @mattkime?

Yes.

For example, if a user selects data stream indices or a data stream index alias, can we surface a callout or maybe some info on a "review" step of the wizard to explain the relationship between index pattern, data stream, and indices? We could also add a link to the data stream docs.

I'm certainly interested in doing this - can you provide advice on how to approach this? I've been focused solely on APIs and haven't considered the user perspective.

[mattkime]

resolved by #70271