[Timelion] Known limitation when multiple index patterns / data views with the same name exist and runtime fields

[lucabelluccini]

Currently, it is known that scripted fields and runtime fields are only supported in metric and split arguments of Timelion (as per https://github.com/elastic/kibana/issues/9022).

There's another limitation, very edge case, when on Kibana:

• We are attempting to use scripted metrics or runtime fields for metric or split arguments of Timelion
• More than one data view / index pattern are defined and match the index argument of Timelion and only one of them defines the scripted metric or runtime field

Example

• Install the sample web logs data set (it has a hour_of_day runtime field)
• Create a second data view hitting kibana_sample_data_logs (it is possible to create more than one data view with the same pattern in recent 8.x version)
• Create a Timelion expression such as .es(index=kibana_sample_data_logs,metric=cardinality:hour_of_day)

You'll notice the visualization will flap from 0 to visualizing the actual data.

It's partially critical as there's no warning or error shown. It would be nice to at least notify the user with a toast message that data might be incorrect in case more than one index pattern / data view is being hit

[lucabelluccini]

Reproduction: https://user-images.githubusercontent.com/87379/205122865-9ebaf2cd-c52e-487d-9aab-8989f56c6b87.mov

[elasticmachine]

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[stratoula]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.