# Elastic APM Agent - Upgrades

**URL:** <https://discuss.elastic.co/t/elastic-apm-agent-upgrades/364785>\
**Category:** APM\
**Tags:** ui\
**Created:** [August 12, 2024, 3:49pm UTC](https://discuss.elastic.co/t/elastic-apm-agent-upgrades/364785 "2024-08-12T15:49:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [August 12, 2024, 3:49pm UTC](https://discuss.elastic.co/t/elastic-apm-agent-upgrades/364785/1 "2024-08-12T15:49:21Z")

</div>

Hello, this is a general question.

From my understanding, APM agents don't have some form of Fleet to manage and upgrade the agents to the latest version. Is this something planned? It feels very scattered to have to go to each service and run upgrade commands.

---

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [August 14, 2024, 7:28am UTC](https://discuss.elastic.co/t/elastic-apm-agent-upgrades/364785/2 "2024-08-14T07:28:05Z")

</div>

Hello Erik,

I don't think this will be possible in the future. In Java (and I guess in .NET is similar), the agent modifies the Java Bytecode using bytebuddy. That means you cannot just replace the old version with a new one so you would need to restart your application.

Your best bet would be to have a CI/CD pipeline where changing the agent version would automatically cause a redeployment of your application with the latest agent. We use the programmatic attachment for that as we can deliver the agent as part of our application.

Best regards  
Wolfram