How you update the Application Real-Time Monitoring Service (ARMS) agent depends on your deployment environment. Find your environment in the following table and follow the corresponding procedure.
| Deployment environment | Update method | Automatic updates |
|---|---|---|
| Enterprise Distributed Application Service (EDAS) | Redeploy the application | No |
| Kubernetes (with ack-onepilot) | Restart application pods | Yes |
| Elastic Compute Service (ECS) with automatic installation | Restart application processes | Yes |
| Manual installation | Download and replace the agent package | No |
Update the agent in EDAS
Redeploy your applications to update the ARMS agent.
Update the agent in Kubernetes
The ack-onepilot component automatically updates the ARMS agent to the latest version. Restart your application pods to apply the update.
Pin a specific agent version
By default, ack-onepilot updates the agent to the latest version. To pin a specific version, see Control the agent version.
Verify the new agent version in a test environment before you roll it out to all applications.
Update the agent in ECS (automatic installation)
For Java applications integrated with ARMS through the automatic installation feature, the ECS plug-in automatically updates the ARMS agent. Restart your application processes to apply the update.
Update a manually installed agent
For Java applications where you installed the ARMS agent manually, download the latest agent package, replace the existing one, and redeploy.
Log in to the ARMS console.
In the left-side navigation pane, choose .
Click the Agent Release Notes tab to find the latest version and its download link.
Download the latest ARMS agent package.
Replace the old agent package with the downloaded one.
Redeploy the application.
What's next
Control the agent version -- Pin a specific agent version for controlled rollouts.