Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hard reload of dashboard required to see the incoming data when they did not initially exist #149093

Open
Tracked by #166175
MichaelKatsoulis opened this issue Jan 18, 2023 · 8 comments
Labels
enhancement New value added to drive a business result Feature:Data Views Data Views code and UI - index patterns before 8.0 Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@MichaelKatsoulis
Copy link
Contributor

Currently when opening a dashboard when there are no data streams yet, then all visualizations show the missing field error.
Example from Kubernetes dashboard where the integration is installed but agent is not running yet.

no data yet

When agent starts running and data start flowing in elasticsearch, the data still do not appear in the visualizations Eno matter how many minutes pass. Auto/Manual refresh have no impact at all.

refresh on, data exist

The only way to see the data and fill the dashboard is by reloading the whole dashboard page via the browser.

after reload

This can be very confusing for a user.
After discussions it seems that this is expected and the reason is that a refresh of the dashboard (either by manually or due to auto-refresh) only fetches the data again, but not the field lists for each involved data view as this would be very wasteful.

A suggested improvement could probably involve special handling of the "no fields" case, so a refresh also reloads the field list (at a potentially high cost for CCS data views).

@MichaelKatsoulis MichaelKatsoulis added enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jan 18, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

@stratoula stratoula added the Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews) label Jan 18, 2023
@elasticmachine
Copy link
Contributor

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

@stratoula stratoula added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jan 18, 2023
@kertal kertal added the Feature:Data Views Data Views code and UI - index patterns before 8.0 label Jan 18, 2023
@drewdaemon drewdaemon added the Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas label Jan 18, 2023
@elasticmachine
Copy link
Contributor

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

@nreese
Copy link
Contributor

nreese commented Jan 18, 2023

Maps has a similar issue open about reloading data views for data streams to fetch new fields, #143877

@mattkime
Copy link
Contributor

A suggested improvement could probably involve special handling of the "no fields" case, so a refresh also reloads the field list (at a potentially high cost for CCS data views).

This is a solid plan. Also, CCS performance issues have been fixed. Let me know if there's anything I can do to help from a data views perspective.

@KOTungseth KOTungseth added the loe:needs-research This issue requires some research before it can be worked on or estimated label Feb 16, 2023
@timductive timductive removed the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Mar 22, 2023
@ThomThomson ThomThomson removed the Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas label Apr 5, 2023
@ThomThomson
Copy link
Contributor

Removing the Presentation team label from this as it looks like this will be accomplished at the Data View level.

@KOTungseth KOTungseth added loe:x-large Extra Large Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed loe:needs-research This issue requires some research before it can be worked on or estimated impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. triage_needed labels Apr 27, 2023
@kertal kertal added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Jun 21, 2023
@markov00
Copy link
Member

markov00 commented Jun 4, 2024

The error messaging will partially be solved by #151526
Currently there is no clean way to detect when a field is populated with the first data point except for polling index mappings until all fields are available in the dashboard

@kertal kertal added the Icebox label Sep 24, 2024
@kertal kertal added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews) labels Oct 22, 2024
@markov00
Copy link
Member

We are wondering why during the integration asset setup/installation step we are not updating the index mappings with the required fields used by the dashboards. If we did that, instead of using dynamic mappings when the first document containing that field reaches ES we could fix that problem at the root level.
Is there any reason why we don't update the index mapping together with the installation of an integration asset?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Data Views Data Views code and UI - index patterns before 8.0 Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests