# Integrations Page in Kibana is too slow and constantly have timeout erros **URL:** \ **Category:** Kibana\ **Created:** [June 23, 2023, 2:59pm UTC](https://discuss.elastic.co/t/integrations-page-in-kibana-is-too-slow-and-constantly-have-timeout-erros/336785 "2023-06-23T14:59:33Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [June 23, 2023, 2:59pm UTC](https://discuss.elastic.co/t/integrations-page-in-kibana-is-too-slow-and-constantly-have-timeout-erros/336785/1 "2023-06-23T14:59:34Z")
Hello, Almost every time I need to use the Integration pages to add a new Integration to the Elastic Agent or update the current ones I have some issues with being too slow or even timing out. I started using Integrations when I upgraded to version 8 on 8.5.1 and now I'm on 8.8.1 and this still happens. Looking at Kibana I have a couple of timeout errors when trying to talk with Elastic Package Registry: ```auto {"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.6.1"},"@timestamp":"2023-06-23T14:48:53.533+00:00","message":"Failed to fetch latest version of gcp from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=gcp&prerelease=false&kibana.version=8.8.1 failed, reason: connect ETIMEDOUT 34.120.127.130:443","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1016},"trace":{"id":"50d907375f3708ad355977a99430ac88"},"transaction":{"id":"4670eca1a4ce0598"}} {"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.6.1"},"@timestamp":"2023-06-23T14:48:53.540+00:00","message":"Failed to fetch latest version of gcp from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=gcp&prerelease=true&kibana.version=8.8.1 failed, reason: connect ETIMEDOUT 34.120.127.130:443","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1016},"trace":{"id":"57cefe40ea0a09d53fc30bdeb01012fb"},"transaction":{"id":"de481089f588fd1b"}} {"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.6.1"},"@timestamp":"2023-06-23T14:48:53.551+00:00","message":"Failed to fetch latest version of gcp from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=gcp&prerelease=false&kibana.version=8.8.1 failed, reason: connect ETIMEDOUT 34.120.127.130:443","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1016},"trace":{"id":"0e4bf8a88ff9e2605821dc813d6ba1dd"},"transaction":{"id":"74ac4269873930a2"}} {"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.6.1"},"@timestamp":"2023-06-23T14:48:56.752+00:00","message":"Failed to fetch latest version of gcp from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=gcp&prerelease=false&kibana.version=8.8.1 failed, reason: connect ETIMEDOUT 34.120.127.130:443","log":{"level":"ERROR","logger":"plugins.fleet"},"process":{"pid":1016},"trace":{"id":"e680a48ff2d7f2f096e594198b9bae1f"},"transaction":{"id":"39f8c228384f7a76"}} ``` > connect ETIMEDOUT 34.120.127.130:443 Which is the `epr.elastic.co` IP address: ```auto Non-authoritative answer: epr.elastic.co canonical name = infra-cdn.elastic.co. Name: infra-cdn.elastic.co Address: 34.120.127.130 Name: infra-cdn.elastic.co Address: 2600:1901:0:1d7:: ``` Is there something I can do on my side to solve this? I need to keep constantly refreshing the Integration page until it loads. ---
**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:** [June 23, 2023, 11:04pm UTC](https://discuss.elastic.co/t/integrations-page-in-kibana-is-too-slow-and-constantly-have-timeout-erros/336785/2 "2023-06-23T23:04:37Z")
Interesting wonder if these 2 are related. > [@Kibana Fleet high CPU Load on Elasticsearch when adding Integrations](https://discuss.elastic.co/t/kibana-fleet-high-cpu-load-on-elasticsearch-when-adding-integrations/336729): > > Since Elastic-Stack 8.8.0 we observe an issue that is reproducible when navigating fleet and especially modifying integrations where the Elastic-Stack Cluster stalls out due to high CPU. In the following screenshot I've tried to add the system integration and the Elasticsearch process goes to 100% CPU load for several minutes. 7 Elasticsearch instances 2 Kibana instances 2 Fleet instances Per Server AMD EPYC 7313 8TB NVME SSD 128 GB Memory Debian 12 It seems as there is a bug in a compo… I pinged internally as well... both got to the internal slack. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [June 24, 2023, 2:41am UTC](https://discuss.elastic.co/t/integrations-page-in-kibana-is-too-slow-and-constantly-have-timeout-erros/336785/3 "2023-06-24T02:41:04Z")
Not sure, I do not have any High CPU load on my Kibana, just a timeout. This has been happening for a long time, first time I had this issue was when we started trying to use integrations as I commented on [this post](https://discuss.elastic.co/t/kibana-cant-connect-to-package-directory/316919/3). It is not a big issue because we had many issues with integrations and decided to use just a couple of them, but it is pretty annoying because this impacts the fleet page as well. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 22, 2023, 2:41am UTC](https://discuss.elastic.co/t/integrations-page-in-kibana-is-too-slow-and-constantly-have-timeout-erros/336785/4 "2023-07-22T02:41:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.