-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Give the ability to set up elastic agent download timeout #121069
Comments
Pinging @elastic/fleet (Feature:Fleet) |
@mostlyjason Could be interesting to expose agent settings at the policy level for:
|
Hi @jlind23 ! About 30% of our elastic agents can't upgrade due to poor internet connection plus download timeout being very low currently (120s). I haven't found a way to modify this setting via fleet either. Would be lovely to have this in the UI. |
Hi @nickbabkin, Did you recently try the new rolling upgrade feature in order to release the network pressure? |
Hi @jlind23, Yes we did, we are geographically distributed and unfortunately in some regions connection is so poor that 150 Mb can't be downloaded within 2 minutes. In what version was download timeout changed to 10 minutes? Maybe I have to manually upgrade our agents to that one first. |
Hi @nickbabkin the default to 10min was introduced by this PR: elastic/elastic-agent#308 |
@jlind23 lovely, thanks! |
We are running 8.4.1 version of the elastic agent here. I am trying to upgrade an agent from 8.4.1 to 8.4.2 and the agent download is taking more than 10 minutes from an internal artifacts location. How do I increase the timeout from 10 minutes to a higher number? |
We are running a geographically distributed company and aren't able to download the agent binaries in 10 minutes too. We would also love to have the ability to set download timeout from the UI. |
As part of the policy we should give the ability to the customer to set up "agent.download.timeout: 10s" through the UI instead of letting them do it in the fleet.yml config.
Fleet UI enhancements:
The text was updated successfully, but these errors were encountered: