# Why we need to scroll to see next records in Discover table of kibana?

**URL:** <https://discuss.elastic.co/t/why-we-need-to-scroll-to-see-next-records-in-discover-table-of-kibana/38844>\
**Category:** Kibana\
**Created:** [January 11, 2016, 7:56am UTC](https://discuss.elastic.co/t/why-we-need-to-scroll-to-see-next-records-in-discover-table-of-kibana/38844 "2016-01-11T07:56:18Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\
**Post date:** [January 12, 2016, 6:50pm UTC](https://discuss.elastic.co/t/why-we-need-to-scroll-to-see-next-records-in-discover-table-of-kibana/38844/7 "2016-01-12T18:50:34Z")

</div>

Hi Vikas,  
You could go to Settings \> Advanced and change discover:sampleSize from the default of 500 to 7000 but use at your own risk. That much data could run your system out of memory or crash something!  
But as far as the Chrome plugin getting all the data without you having to scroll down, I'm not sure.

It looks like there have been several attempts to get data from Elasticsearch directly into Excel Here's one;

> **[Smarte Analyse von Log-Daten mit Excel und ElasticSearch](http://www.bigdata-unleashed.com/20140708/smarte-analyse-von-log-daten-mit-excel-und-elasticsearch)**
>
> Data-Scientists möchten mit den Unternehmensdaten auch ohne aufwändige IT-Projekte jonglieren, um Erkenntnisse für Analysten und Stakeholdern zu gewinnen und bereitzustellen. Doch wie können Self-Service-Analyse-Tools wie Excel dazu verwendet werden,...

  
If it's a static query you need to run often to get latest data, I would try to find a more direct solution like this.

Lee

---

_[View the full topic](https://discuss.elastic.co/t/why-we-need-to-scroll-to-see-next-records-in-discover-table-of-kibana/38844)._
