Visualizations request wrongly default index pattern on dashboard

[timroes]

When having a dashboard with just one TSVB visualization at it that's not using the default index pattern, TSVB will still send out a request to load the fields of the default index pattern:

In this screenshot the default index pattern is ecommerce but the vis uses logs, but as you can see we still request fields for both. The filters dialog will btw show correctly only fields from logs.

This happens no matter whether the vis uses string mode or index pattern mode.

That additional request can cause annoying permission errors, in case the users of the dashboard don't have permissions to the default index pattern, see also https://discuss.elastic.co/t/privilege-issue-opening-dashboard-always-requests-the-default-index-pattern/278274

[elasticmachine]

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

[alexwizp]

@timroes For me it looks more like a Dashboard problem. I think the root cause of that issue in lazy initialization of embeddable visualizations, as a result, at the initial moment we do not have an understanding of which indexes will be used. And then after the visualization is ready we update our state. This might explain the query for getting the default index

To test my theory, I created a new dashboard with two classic visualizations (not TSVB!) and added a console.log in src/plugins/dashboard/public/application/lib/sync_dashboard_index_patterns.ts. Let's see what we got:

Logic happens 3 times and for first one we load a default index. See next condition

Last screen in a manner which you did for description. Absolutely the same but without TSVB

I think it's not so difficult to fix, but @ThomThomson can someone from your team take this one?

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)