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

auto refresh service #21150

Closed
nreese opened this issue Jul 24, 2018 · 0 comments
Closed

auto refresh service #21150

nreese opened this issue Jul 24, 2018 · 0 comments
Labels
stale Used to mark issues that were closed for being stale Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@nreese
Copy link
Contributor

nreese commented Jul 24, 2018

There are currently several places in Kibana that manage their own auto refresh logic. This includes courier, timelion, and several locations in x-pack.

Courier's SearchPoll has logic to throttle the refresh interval timeout to the speed that courier can execute when the interval is too fast.

All auto refresh logic should to be combined into a single service. This service should use the SearchPoll logic so that the refresh timer can be throttled to the speed for the slowest request when the interval is too fast.

This issue is created in response to #20863. 20863 introduced a temporary fix for auto refreshing visualization panels in dashboard. Part of the converstation for the temporary fix involved creating a proper auto refresh service. The event autoRefreshFetch should be replaced by the auto refresh service

@nreese nreese added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Jul 24, 2018
@joshdover joshdover added the stale Used to mark issues that were closed for being stale label Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Used to mark issues that were closed for being stale Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

2 participants