Warning on data histogram when selected field does not match default time field in index pattern

[ppf2]

Consider the following scenario.

The default time field for the associated index pattern is set to another (custom) date field that is not @timestamp while the date histogram is referencing @timestamp. The date picker for this visualization is set to Last 15m.

With the mismatch in index pattern time field and the field selected for the date histogram. This resulted in a very large number of data points being returned (with many outside of the date picker Last 15m range - unintended behavior). When this visualization is added to a dashboard, the entire dashboard locks up for >1 hour on loading (the browser tab has to be terminated).

It will be helpful to show a warning (some form of validation) when a date histogram is configured with a time field that is not matching up with the default time field set against its index pattern.

[mattkime]

I'm going to do an investigation into this problem - #84792

I think index pattern consumers need a way of expressing what fields they're dependent upon. It'll be a significant change between index patterns api and index pattern consumers.

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[ghudgins]

We believe this is mitigated in how Lens works - using a non-default date field will update the time picker to filter using the same field as the one selected. Please re-open this issue if you feel Lens does not solve this.

Since this would require a large development effort to implement in Visualize/TSVB and our efforts are focused on extending the functionality of Lens in easy-to-use and consistent way. We aim to provide the best possible visualization editing experience in Lens and are working to improve that tool and help users migrate.