-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Refresh all dashboard items #3609
Labels
enhancement
New feature or request
feature/dashboards
Feature Tag: Dashboards
P1
Urgent, non-breaking (no crash but low usability)
Comments
paolodamico
added
bug
Something isn't working right
feature/dashboards
Feature Tag: Dashboards
labels
Mar 9, 2021
2 tasks
Excellent - this is a big usability issue when training marketing people to use graphs. Makes them not trust the data and regress to other tooling. <3 Short term fix is to 'hard refresh' and it tends to work for anyone who's finding this too frustrating in the meantime. |
4 tasks
We should also add an auto-refresh option for dashboards |
paolodamico
added
P1
Urgent, non-breaking (no crash but low usability)
enhancement
New feature or request
and removed
bug
Something isn't working right
labels
May 13, 2021
paolodamico
changed the title
Bug refreshing all dashboard items
Refresh all dashboard items
May 13, 2021
This is gonna be needed for instance status dashboard. |
2 tasks
macobo
added a commit
that referenced
this issue
Jun 4, 2021
Also `internal` dashboard always refreshes all. How it works under the hood - if refresh param is passed, we call cache updating code before returning the cached results. This bypasses the need to fetch data from /api/insight and other endpoints which are not embedding-aware Mostly solves #3609 and provides a workaround for #4587
macobo
added a commit
that referenced
this issue
Jun 10, 2021
Also `internal` dashboard always refreshes all. How it works under the hood - if refresh param is passed, we call cache updating code before returning the cached results. This bypasses the need to fetch data from /api/insight and other endpoints which are not embedding-aware Mostly solves #3609 and provides a workaround for #4587
macobo
added a commit
that referenced
this issue
Jun 10, 2021
) * Re-add refresh button, respect refresh in API Also `internal` dashboard always refreshes all. How it works under the hood - if refresh param is passed, we call cache updating code before returning the cached results. This bypasses the need to fetch data from /api/insight and other endpoints which are not embedding-aware Mostly solves #3609 and provides a workaround for #4587 * Show "last refresh time" in dashboard. * Remove individual refresh buttons according to TODO * Add tests * mypy fix * fix UI Co-authored-by: Paolo D'Amico <paolodamico@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
feature/dashboards
Feature Tag: Dashboards
P1
Urgent, non-breaking (no crash but low usability)
Bug description
Support refreshing all dashboard items. This feature was temporarily removed because it wasn't working properly)
Expected behavior
items
object in thedashboardLogic
should contain the latest information.How to reproduce
Environment
Additional context
Follow-up to #3363
Technical context
When refreshing all dashboard items (via
refreshAllDashboardItems()
) not all items are consistently refreshed all the time. Tested for instance with a dashboard with a couple of mixed (different type) graphs. Some items are still kept on "last refreshed 10 minutes ago".In addition to the above, as originally reported on #3608, when calling
refreshAllDashboardItems
we update each item in their own scope, which means that the generalitems
object in the upper scope logic (dashboardLogic.js
) doesn't get updated. Not sure if we should propagate the change upwards, re-fetch everything, or just do a general refresh.The UX problem this is causing is that the "Last refreshed" label now introduced in the dashboards gets outdated because
items
doesn't get updated. Having this object with outdated information also leads to other confusing UX issues.Thank you for your bug report – we love squashing them!
The text was updated successfully, but these errors were encountered: