# Kibana Fleet high CPU Load on Elasticsearch when adding Integrations

**URL:** <https://discuss.elastic.co/t/kibana-fleet-high-cpu-load-on-elasticsearch-when-adding-integrations/336729>\
**Category:** Kibana\
**Tags:** fleet\
**Created:** [June 22, 2023, 11:56pm UTC](https://discuss.elastic.co/t/kibana-fleet-high-cpu-load-on-elasticsearch-when-adding-integrations/336729 "2023-06-22T23:56:26Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![matled](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@matled](https://discuss.elastic.co/u/matled)\
**Post date:** [June 30, 2023, 11:27am UTC](https://discuss.elastic.co/t/kibana-fleet-high-cpu-load-on-elasticsearch-when-adding-integrations/336729/10 "2023-06-30T11:27:34Z")

</div>

I've opened up a dedicated thread for this issue:  
[Elastic Integrations fail to install and lead to broken Dashboards when used with multiple Kibana Spaces - Elastic Stack / Kibana - Discuss the Elastic Stack](https://discuss.elastic.co/t/elastic-integrations-fail-to-install-and-lead-to-broken-dashboards-when-used-with-multiple-kibana-spaces/337246)

---

_[View the full topic](https://discuss.elastic.co/t/kibana-fleet-high-cpu-load-on-elasticsearch-when-adding-integrations/336729)._