Integrations Page in Kibana is too slow and constantly have timeout erros

Elastic Stack Kibana
1

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:

{"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:

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.

2

Interesting wonder if these 2 are related.

I pinged internally as well... both got to the internal slack.

3

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.

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.

4

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