[Discover] Field Statistics rollout by default

[ryankeairns]

Meta issue to track remaining work for Field Statistics by default rollout.

Required for rollout by default

• [ML] Add Index data visualizer grid embeddable as extra view within Discover #107184
• Design fixes [Discover] Field statistics design issues  #117602
• Enumerate research tasks (need to draft plan; otherwise hidden in adv settings)
• Fix for data views with lots of fields Performance problem of Data Visualizer in Discover for large index patterns #119759

Noted in PR above as follow-ups- are these needed for rollout as default? If so, convert to checklist items

• Support for search sessions/Make it slow to help the user experience better, especially when index contains a lot of fields
• Placement of the toggle/controls ([Discover] Add "Chart options" menu #112149)
• Sample size control/show empty fields control
• Prevent scroll bars whenever Aggregated view is on (Related EUI issue [EuiScreenReaderOnly] Add clip property to fix scrolling bug eui#5152)
• Document count and % is abnormally high for some indices (Related elasticsearch issue Sampler aggregation returns high filter doc_count  elasticsearch#77575)
• Functional tests

Note: Add any bugs (from below) that are considered blockers.

---

Field Stats (aka Data Visualizer) bugs

The following bugs/issues are classified by their severity and impact relative to Discover.

Medium

• Add

Medium/Low - need further evaluation

• Add

Low

• Add

---

Further Field Statistics related work

• https://github.com/elastic/ml-team/issues/604

[elasticmachine]

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

[ryankeairns]

@andreadelrio how do you feel about the remaining items in #117602 ? The placement question we've discussed may take more time and thought (feels like a potentially large change), but I'm curious about the other items in that issue in terms of priority / need prior to displaying this feature by default.

There are other product questions to be considered, as well, but I'm wanting to iron out our design recommendations separately. Thanks!

[andreadelrio]

@andreadelrio how do you feel about the remaining items in #117602 ? The placement question we've discussed may take more time and thought (feels like a potentially large change), but I'm curious about the other items in that issue in terms of priority / need prior to displaying this feature by default.

There are other product questions to be considered, as well, but I'm wanting to iron out our design recommendations separately. Thanks!

@ryankeairns Regarding the placement, Quynh and Peter seemed to like the option I mocked where we add a "Switch to field statistics" link to DataGrid but we agreed it would be better to wait until DataGrid is turned on by the default.

@qn895 was also going to follow up with their docs person regarding what text we can use in the tooltip for text fields. I'll follow up with her when she's back in office. I'm missing that in order to implement the tooltip which will hopefully help clarify why we don't show stats for text fields.

[kertal]

@ryankeairns we rolled out field statistics, and there has not been much activity, are you fine with closing this?

[ryankeairns]

I'll close this issue as the feature is now there by default, but it does beg the question why there has not been much activity.
cc:/ @ninoslavmiskovic