# Limited resources usage per dashboard

**URL:** <https://discuss.elastic.co/t/limited-resources-usage-per-dashboard/191603>\
**Category:** Kibana\
**Created:** [July 22, 2019, 8:25am UTC](https://discuss.elastic.co/t/limited-resources-usage-per-dashboard/191603 "2019-07-22T08:25:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eyal\_Even](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eyal_even/32/49885_2.png) [@Eyal\_Even](https://discuss.elastic.co/u/Eyal_Even)\
**Post date:** [July 22, 2019, 8:25am UTC](https://discuss.elastic.co/t/limited-resources-usage-per-dashboard/191603/1 "2019-07-22T08:25:44Z")

</div>

I have a rather small cluster, but one of my indices takes about 55GB per day, and its life cycle goes 1 month back.  
I have users trying to query that index for the entire 1 month back, but it takes too much off of my CPU power and it eventually crashes my Kibana or it slows down to a crawl.  
I have 5 nodes, each one has 8 cores and 8GB of RAM.  
I'd like to know if there is a way of limiting the resource usage of certain dashboards. The users who go a month back don't need immediate results, they just need to eventually see the bigger picture.  
Weather its limiting the resource usage each user can have, or limiting the resource usage a dashboard can use, I'd like to find a way to limit my users/dashboards from destroying my cluster.  
Any help is appreciated, and thanks for reading

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [July 22, 2019, 3:20pm UTC](https://discuss.elastic.co/t/limited-resources-usage-per-dashboard/191603/2 "2019-07-22T15:20:08Z")

</div>

Hello,

Did you consider adding a roll\_up index pattern and limiting the fields the user can use?  
[https://www.elastic.co/guide/en/kibana/current/data-rollups.html](https://www.elastic.co/guide/en/kibana/current/data-rollups.html)

Thanks,  
Bhavya

---

<div class="post-metadata">

**Author:** ![Eyal\_Even](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eyal_even/32/49885_2.png) [@Eyal\_Even](https://discuss.elastic.co/u/Eyal_Even)\
**Post date:** [July 23, 2019, 6:21am UTC](https://discuss.elastic.co/t/limited-resources-usage-per-dashboard/191603/3 "2019-07-23T06:21:21Z")

</div>

Thanks, I will try that out and let you know if it works

---

<div class="post-metadata">

**Author:** ![Eyal\_Even](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eyal_even/32/49885_2.png) [@Eyal\_Even](https://discuss.elastic.co/u/Eyal_Even)\
**Post date:** [July 25, 2019, 12:49pm UTC](https://discuss.elastic.co/t/limited-resources-usage-per-dashboard/191603/4 "2019-07-25T12:49:50Z")

</div>

It seems like the rollup doesnt even work, I looked it up and after understanding more about it, I tried it out for myself but the index doesnt even seem to rollup. is there maybe a bug in my version? I'm using 7.1.1 and i followed the official page exactly (even tried the api as well)

Thanks, Eyal

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 22, 2019, 12:50pm UTC](https://discuss.elastic.co/t/limited-resources-usage-per-dashboard/191603/5 "2019-08-22T12:50:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.