# Elastic Cloud | How and why to handle Kibana resources when creating deploy

**URL:** <https://discuss.elastic.co/t/elastic-cloud-how-and-why-to-handle-kibana-resources-when-creating-deploy/305838>\
**Category:** Kibana\
**Created:** [May 27, 2022, 11:19pm UTC](https://discuss.elastic.co/t/elastic-cloud-how-and-why-to-handle-kibana-resources-when-creating-deploy/305838 "2022-05-27T23:19:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![caraboy](https://avatars.discourse-cdn.com/v4/letter/c/b2d939/32.png) [@caraboy](https://discuss.elastic.co/u/caraboy)\
**Post date:** [May 27, 2022, 11:19pm UTC](https://discuss.elastic.co/t/elastic-cloud-how-and-why-to-handle-kibana-resources-when-creating-deploy/305838/1 "2022-05-27T23:19:05Z")

</div>

I am wondering which would be the reasons/use-cases that would require to assign Kibana high RAM, CPU and zone resources.

I mean, it's clear what does this means for Elasticsearch component (I/O efficiency). But how these variables affect Kibana performance? What different use cases there are where these resources might/must be handled differently?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/c/9c74c308b8fc021adde945c45b5d347e111d75ba.png)  
Thank you in advance.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 27, 2022, 11:44pm UTC](https://discuss.elastic.co/t/elastic-cloud-how-and-why-to-handle-kibana-resources-when-creating-deploy/305838/2 "2022-05-27T23:44:28Z")

</div>

Hi @caraboy

Use Cases Could Include any Combination of the Following.. all these use more CPU and RAM in Kibana

- More Users / Concurrent Users doing Searches, Discover, Dashboards, Visualizations, Using the SIEM and or Observability Apps etc.
- More Alerts - Alerting runs in Kibana ... Large scale alerting can consume significant resources
- More Reporting - Reports are Generated Via Kibana

---

<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:** [June 24, 2022, 11:44pm UTC](https://discuss.elastic.co/t/elastic-cloud-how-and-why-to-handle-kibana-resources-when-creating-deploy/305838/3 "2022-06-24T23:44:30Z")

</div>

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