[Fleet] Integrations grid takes a long time to load when EPR endpoint does not respond

elastic / kibana

Your window into the Elastic Stack

https://www.elastic.co/products/kibana

Other

19.63k stars 8.22k forks source link

[Fleet] Integrations grid takes a long time to load when EPR endpoint does not respond #128130

Open jloleysens opened 2 years ago

jloleysens commented 2 years ago

Currently, the integrations page can be slow because it tries to pull new packages from EPR before displaying anything. It would be a really nice enhancement to "stream in" content as it arrives rather than block on first fetching everything since the request to EPR can be slow, or unavailable in certain scenarios.

This is especially true if users want to use some of the packages before having set up Elastic agents.

elasticmachine commented 2 years ago

Pinging @elastic/fleet (Team:Fleet)

joshdover commented 2 years ago

Refinement notes:

It's unclear how this is happening, the customer provided HAR does not show any requests taking 15 minutes as reported.
When there is no EPR access, usually this page fails pretty fast and falls back to the EPR offline instructions
Maybe there's some retry logic that is backing up multiple times?

One way to fix this would be to show the non-EPR cards immediately and then update the grid once the EPR response comes back.

joshdover commented 2 years ago

@hop-dev was able to reproduce some slowness (6+ minutes) in the case where Kibana can connect to the EPR endpoint but doesn't get a response back from the server. This could indicate an issue with a proxy or other network configuration. It'd be nice if we could provide a better experience here with a more aggresive timeout (2 minutes?), but I think this is fairly low priority for now unless we see this to be more widespread.