Index pattern creation UX: Simplify index-pattern creation form

[cjcenizal]

Remove "Index contains time-based events" checkbox

#11419 (merged)

Per @skearns64, we can remove this checkbox and just provide a "Don't use time field" option in the dropdown.

Remove "Expand index pattern when searching" checkbox

Remove UI for creating index patterns based on event times

[skearns64]

I wonder if we should be slightly more explicit with the label name - "Time Field" feels a bit ambiguous - I may have several date fields in my index. I find "Default Time Field" to be a little more intuitive - this is the time field that will be used by default for this index pattern.

If we do change the label to "Default Time Field", then we should think through what the first entry in the dropdown should be - maybe something like "No Default Time Field"

[uboness]

"Default Time Field" or another option can be "Time Filter Field" (which basically describes what its used for) ?

Also, we can even be a bit smarter and if there is not time field for the defined pattern, the dropdown remains disabled and shows nothing.

Also, very important IMO, one of the problems you have today, is that it may take quite some time between the time the user enters the index pattern to the time we resolve all the optional time fields and populate the dropdown. Today there's no indication that this is being processed in the background, and further more, with this change, it'll be even harder to know if a) the entered index pattern simply doesn't have a time field, or b) it's still working on resolving the fields. We should add a spinner next to the dropdown (on its right) that will spin as long as we're resolving the fields.

[cjcenizal]

@uboness see #10439 re spinner and loading feedback.

[uboness]

@uboness see #10439 re spinner and loading feedback.

ha... perfect

[skearns64]

Also, we can even be a bit smarter and if there is not time field for the defined pattern, the dropdown remains disabled and shows nothing.

I personally prefer the consistency of having the "Default Time Field" dropdown to always have the same value when it means the same thing. If I have an index with no date fields, I would want to see the dropdown (disabled or enabled doesn't matter) saying "No Default Time Field". If I do have date fields, I would want the first item in the dropdown to always be "No Default Time Field", so if I choose to have no default date field, it looks the same.

[uboness]

I personally prefer the consistency of having the "Default Time Field" dropdown to always have the same value when it means the same thing. If I have an index with no date fields, I would want to see the dropdown (disabled or enabled doesn't matter) saying "No Default Time Field". If I do have date fields, I would want the first item in the dropdown to always be "No Default Time Field", so if I choose to have no default date field, it looks the same.

I'm good with that too... as long as we keep the dropdown disabled if there's not even one date field

[cjcenizal]

Per conversation with @ycombinator, we're going to aim to get this in for 6.0.

We will not implement the "3 form solution" (#10026).

Before moving forward with this issue, we need to ensure that users won't miss the functionality that the "Expand index pattern when searching" checkbox provides, or be impacted performance-wise. Review concerns raised by @Bargs and @epixa in:

• Index pattern creation UX: Remove UI for creating index patterns based on event times #10443
• Cross-cluster search support #11011
• Index pattern creation UX: Remove "Do not expand index pattern" checkbox #10445
• No need to use Field Stats API in the dashboard and visualise tabs (and possibly Discover too) #6644

[epixa]

I don't think there is any way to tell for sure whether people will miss that functionality or not, but I do think it's too early to say one way or another. Given our past experience with changes in this area, I don't think we can realistically remove the field_stats behavior entirely in 6.0, though we should deprecate it. Starting in 5.4.0, the field_stats behavior is no longer the default option for new index patterns, so deprecating it is the logical next step.

[cjcenizal]

I think everything in here has been addressed by now.