-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Serverless] [Unified Search] Increase minimum refresh interval to 5s. #176256
Comments
Pinging @elastic/kibana-visualizations (Team:Visualizations) |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
This seems to be an eui component https://eui.elastic.co/#/forms/auto-refresh#refresh-interval, and not sure if the interval settings are configurable. |
Blocked by eui improvement elastic/eui#7512 |
Pinging @elastic/kibana-presentation (Team:Presentation) |
Are we talking about a minimum for the component only, or also for the refresh behavior itself? Right now, at least in Discover, you can modify the state in the URL to even get sub-1s values ( |
Could call @lukasolson, I think we should catch such values by better validation on consumer side |
@thomasneirynck I notice you assigned the @elastic/kibana-presentation team to this. Is the idea here that only dashboard would have this limit, and we'd need to pass a prop into the Unified Search bar? Does it also require work on the Unified Search side to allow for this prop to be passed in, and for validation to prevent sub-1s refresh intervals from being injected? |
yes, and only for Serverless. As far as team assignment, I had to pick something :)
Both. Dashboards should not trigger such fast refreshes in any scenario. |
Improvement merged in Eui elastic/eui#7516. Removed blocked label. |
Describe the feature:
5s should be minimum for the refersh setting. Currently it is 1s
Describe a specific use case for the feature:
1s adds needless strain on resources. 5s is more sensible guideline.
More context here https://github.com/elastic/kibana-team/issues/745
The text was updated successfully, but these errors were encountered: