Specify the agent version to ensure compatibility - Microservices Engine

This topic describes how to specify the version of the Microservices Governance agent in Microservices Engine (MSE).

View the version of the MSE agent

Log on to the MSE console, and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Governance > Application Governance.
On the Application list page, click the resource card of the destination application.
In the left-side navigation pane, click Node details.
In the All Nodes section, click the desired node. On the Basic Information tab, view the agent version in the Probe Version column.

Specify the agent version by using the ack-onepilot component

Prerequisites

The ack-onepilot component of a version later than 3.0.16 is installed. If the version of the installed ack-onepilot component is 3.0.16 or earlier, upgrade the component by following the instructions in Update the Microservices Governance component.

Procedure

If you do not specify the agent version, the agent of the latest stable version is used. If you specify the agent version, use the agent of the specified version to enable Microservices Governance for your application. You can download the agent package from one of the following endpoints:

Public endpoint: http://arms-apm-${regionId}.oss-${regionId}.aliyuncs.com/${agentVersion}/ArmsAgent.zip
Internal endpoint: http://arms-apm-${regionId}.oss-${regionId}-internal.aliyuncs.com/${agentVersion}/ArmsAgent.zip

For the pod in which your application resides, configure aliyun.com/agent-version: agent version in labels to specify the agent version.
If you want to use the agent of version 3.2.9 for a pod, add labels to the YAML file of the deployment. Sample code:
```
spec:
 template:
   metadata:
     labels:
       aliyun.com/agent-version: "3.2.9"
       mseNamespace: "default" # The MSE microservice namespace to which your application belongs. 
       msePilotCreateAppName: "<yourAppName>" # Replace <yourAppName> with the actual name of your application.
```
Note
- For more information about the versions and features of the agent, see Release notes for the Java agent.
- We recommend that you manually download the agent package and confirm that the required agent version exists before you specify the agent version.
Run the cat /home/admin/.opt/ArmsAgent/version command for the related pod to confirm the agent version in use.
After you complete the preceding step and restart your application, confirm the agent version in use on the Node details page of the application.

Specify the agent version by using ECS instances

If you want to enable Microservices Governance by using ECS instances, you can download the agent package of the required version, and enable Microservices Governance for your application. For more information, see Enable Microservices Governance for microservice applications on ECS instances.

You can download the agent package from one of the following endpoints:

Public endpoint: http://arms-apm-${regionId}.oss-${regionId}.aliyuncs.com/${agentVersion}/ArmsAgent.zip
Internal endpoint: http://arms-apm-${regionId}.oss-${regionId}-internal.aliyuncs.com/${agentVersion}/ArmsAgent.zip

Note

In the endpoints, regionId specifies the ID of the region. Examples: cn-hangzhou and ap-southeast-1. For more information, see Supported regions.
agentVersion specifies the agent version. Example: 3.2.9. For more information, see Release notes for the Java agent.
In a virtual private cloud (VPC) environment, you can access the agent by using an internal endpoint. In a non-VPC environment, we recommend that you download the agent package by using the public endpoint.
To download the MSE agent package of the specified version for applications in the China East 1 Finance region, submit a ticket.