[Lens] Don't block render on missing field validation errors

[flash1293]

Currently a Lens chart isn't rendering at all if a field used somewhere in a configuration is missing. This is prudent but can be too strong of a tool because there are a lot of cases where a missing field does not invalidate the whole visualization panel:

• Index mappings are not set up yet but will be soon by an automated process
• A data series / column in a table is optional and if the field doesn't exists it can simply stay empty, the rest of the chart is still valuable

To capture this better, this should be a non-render-blocking error (pattern will be introduced as part of #147485) both on dashboard panels and in the editor.

The dimension with a missing field should still be highlighted in the editor.

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

[angorayc]

Security Solution has similar request:
I have a field, source.ip which has conflict type text and keyword, it shows error in Lens when doing aggregation, but in Dev tools and all the Elasticsearch api does not show error in this case. Would like to know if there’s a chance we could align the rendering logic of Lens with the search result?
Asking because Security Solution is migrating charts rendering with Elastic charts to Lens Embeddables. The current charts fetches data with Elasticsearch api, therefore shows no error when aggregating on a conflict field, but Lens Embeddables shows error on the conflict field. We’d like to fix this inconsistency as conflict fields are actually quite common from users, it might be a bit frustrating if we show error when aggregating on conflict fields.

[flash1293]

I think it would make sense to treat conflict fields like missing fields in this context.

[flash1293]

Another related case is a data view that doesn't have any matching indices - most likely this is a transitory thing, so we could treat it in the same way (show a warning instead of erroring out)

[mlunadia]

Hi team, the combination of this issue with the error toast messages is making Kubernetes dashboards very unappealing. In the Kubernetes world having zero of a resource is not uncommon

[ruflin]

Is there some progress on this? This causes issues like elastic/integrations#4972 (comment)

[dej611]

@andrewctate is working on the task with #147818

[drewdaemon]

@ruflin this particular issue does not cover the error toasts — just not blocking the visualization render if a field or index is missing. Error toasts are a more global issue that has been prioritized more broadly in Kibana.