[Logs UI] Frozen indices support

[alvarolobato]

Implement support for Frozen Indices.
This likely means having solutions follow the Kibana space saved object setting for including frozen indices in queries or not

cc. @makwarth we need a better definition on what we need to do here.

[elasticmachine]

Pinging @elastic/infrastructure-ui

[weltenwort]

The warnings about poor performance in the ES docs suggest to me that it should be opt-in setting. The incremental nature of the log scrolling might interact poorly with the execution semantics of frozen indices. We might want experiment with this first before making specific plans.

[makwarth]

AFAIK, Kibana's saved object setting for frozen indices will be set to off on default.
Can you confirm, @alexfrancoeur ?

[alexfrancoeur]

Yes, this setting will be off by default initially. More details here: #26244

cc: @AlonaNadler

[makwarth]

Thanks @alexfrancoeur.

[AlonaNadler]

It would help to understand what is the observability requirements around this feature. In the first phase in Kibana we plan to have a global setting which will be space specific and turned off by default from querying frozen indices. When turned on, if the query reaches time range which has frozen indices it will query the frozen indices in addition to the regular indices.

[weltenwort]

From the design and engineering perspective two questions come to mind:

• For which kind of query performed in the apps are the performance characteristics exhibited by frozen indices suitable?
• What is the API to get the value of the aforementioned space-specific setting?

[alvarolobato]

We agreed to follow the advanced setting search:includeFrozen added in #27297

[weltenwort]

#25938 demonstrates accessing the uiSettings service to read advanced settings