Open dedemorton opened 2 years ago
Pinging @elastic/fleet (Feature:Fleet)
Pinging @elastic/fleet (Team:Fleet)
@dedemorton Do you have a suggestion for a revised copy? We can get this done pretty quick.
@elastic/ux-writers Can you help with the text here?
Hi, thanks for pinging UX Writers. I'd like to suggest the following changes:
List of sources used by Elastic agents to download their binaries. The default source applies to all agent policies that don't have a specific binary source specified.
https://artifacts.elastic.co/downloads/
Enter the address of the directory containing the binaries to download. Learn more
Let me know if you think these suggestions help addressing the issue. I'm happy to iterate if needed
Kibana version: 8.4.0 (snapshot from 8/16)
Elasticsearch version: 8.4.0
Describe the problem: The text descriptions for the new agent binary download UI under Fleet -> Settings needs some work, specifically:
and
The descriptions make it sound like users are providing the path to a single binary, but it's really an artifact registry that contains all the binaries needed to upgrade Elastic Agent, including Beats, APM, endpoint.
Some users will figure this out by looking at the default setting, but once they try to add an agent binary source, the text makes it sound like they could provide the path to a single binary. They might not realize they need to download a bunch of packages to make this work, especially if the don't bother to look at the docs.