-
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
Per-panel saved search sample size #3220
Comments
the search panel seems to have a big impact on overall speed of dashboard, esp if user has higher latency to servers. In one simple dashboard with fairly large docs (~5KB), all panels load in 30ms but the search panel takes 30 seconds, making dashboard tough to use. |
ya, and i really miss the collapsible panels in K3, though I know you guys changed design. But the collapsible rows really make the dashboard easy to use. Now I have to do lots of scrolling. |
When adding a saved search to a dashboard, it would be very useful to be able to control the sample size as well as page size used on this particular dashboard rather than just have it driven off the global configuration parameter. |
+1 |
Seeing this issue again, where Kibana is far away from the ES cluster (+100ms) and the search panel makes the dashboard very slow (minutes). It doesnt seem like it is possible to paginate like in discover, and going to discover disrupts the flow a lot. The only solution is to use 1 ES cluster per location + a queue for distant replication. What do you think? Thanks |
+1 on this. Tried to manually add a |
+1 |
+1, It would be a really nice feature. |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
Dupe of #4060. |
Nice feature to have. Set size for individual saved search. |
Is this implemented? |
Comment on #4060 to upvote |
I have a dashboard saved search panel showing individual documents. My users are only interested in the most recent ones, but if they extend the dashboard date range, this saved search returns thousands of results, unnecessarily, slowing it down. |
…th a saved search (#157269) - Closes #94140 - #11758 - #4060 - #3220 - #23307 - Closes #131130 ## Summary This PR allows to change current sample size right from Discover page, no need to modify the global default value. Saved search panels on Dashboard will also use the saved value to fetch only the requested sample size. This customisation was requested by many customers as it will allow to load Dashboards faster. Current range for the slider: from 10 to 1000 (with a step 10). <img width="400" alt="Screenshot 2023-10-09 at 11 10 52" src="https://github.com/elastic/kibana/assets/1415710/74e2e4ad-9929-4a44-8d85-c2baafccbaa6"> ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [x] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers)
Implemented via #157269 and will be available in 8.12 |
In K3 we could control paging and how many to query. But K4 the saved search always tries to load the entire data and slows the entire dashboard down. I tried to change the query to put a limit on size in the settings but looks like it doesn't work.
The text was updated successfully, but these errors were encountered: