We replaced all of the filebeat and winlogbeat agents with Elastic Agent, in order to better manage versions.
Currently we are using version 8.17.2 after an upgrade from 8.17.1. We ran into some issues with upgrades of agents on some smaller Linux machines because of the space needed for the previous agent, new download, new agent and the agent not removing the downloads folder after a previous unsuccesful upgrade.
For Linux the Elastic Agent 8.17.1 to 8.17.2 upgrade took about 3.5GB. After a successful install it takes up 1518MB (1448MiB) of disk space.
On the elastic agent installation page it says size on disk should be 1060 MB for version 8.15 and further size reductions were planned.
(Install Elastic Agents | Fleet and Elastic Agent Guide [8.17] | Elastic)
I'm not sure why the 8.17.2 Agents in our setup take about 50% more space than advertised. Does anyone know what we could have missed in the configuration?
After a successful install after a failure due to diskspace it seems the downloads folder located at /opt/Elastic/Agent/data/elastic-agent-/downloads remains on disk. In that case the /opt/Elastic/Agent takes up 1823MB (1739MiB). This feels counterintuitive.
Does anyone know of a Fleet setting that counteracts this behaviour?