"Refresh Dashboard" doesn't refresh the dashboard, only refreshes the visible portion of the dashboard

Grafana Dashboards
1

Hi,

I have a dashboard with a large number of panels that does not all fit on the screen at once. When I press the “refresh dashboard” button, the panels visible on the screen refresh. However if I scroll down a few minutes later to look at panels that weren’t visible on my screen, these have not been refreshed and do not refresh until I look at them.

I have seen a github post semi-related: [Feature request] Introduce settings for refreshing tabs in background · Issue #8113 · grafana/grafana · GitHub that has many people requesting support for grafana to allow auto-refresh when the tab is in background. However, I am wondering why grafana does not refresh the dashboard when the tab is in focus and I press refresh dashboard.

Is it possible to change the settings such that “refresh dashboard” refreshes the dashboard rather than just the currently visible panels?

2

The Grafana documentation is also very clear this isn’t how it should behave:

" Click the Refresh dashboard icon to immediately run every query on the dashboard and refresh the visualizations."

Clicking refresh dashboard does not immediately run every query on the dashboard, it only immediately runs every query on visible panels. I guess this is a bug then since the behaviour disagrees with documentation/it’s name.

3
4

Hi, thank you this says “Lazy loading is enabled by default”, how do I disable this setting?

Also the documentation should be updated since the default behaviour does not follow what the documentation claims.

5

enabled by default means you can’t turn it off

other users also asking for this to be a toggle feature:

6

Oh… I would assume “default” means there are other settings besides default.

Is it intended to add a toggle? Why would this feature be considered to be added without a toggle? It is clearly a very bad feature in many cases.

(also again as mentioned the documentation of ‘refresh dashboard’ is now just flat out wrong, as is its name).

7

if you really want it badly, fork it and implement that specific feature as a dockerized image