This topic provides answers to frequently asked questions (FAQ) about Application Real-time Management Service (ARMS) Application Monitoring.

Overview

Is the ARMS agent compatible with the agents of other APM services, such as Pinpoint?

The ARMS agent is incompatible with the agents of other application performance management (APM) services. APM is implemented by using bytecode instrumentation based on the ASM framework. If you install two agents, bytecode instrumentation is performed twice on the code. Agents developed by different vendors use different code to implement bytecode instrumentation. Performance issues may occur due to code conflicts if you install multiple agents. Therefore, we recommend that you do not install the agents of other APM services.

[Back to Top]

What do I do if the "OutOfMemoryError" error is reported when I start an application after an ARMS agent is installed?

Add the corresponding heap memory parameters to the start command to increase the memory of the Java virtual machine (JVM). In the following example, the initial size (Xms) of the heap memory is 512 MB and the maximum size (Xmx) of the heap memory is 2 GB.

Note You can adjust the sizes based on your actual requirement. In other environments such as Tomcat, add this parameter to JAVA_OPTS in the configuration file. 
   -Xms512M
   -Xmx2048M

If the OutOfMemoryError: PermGen space error is reported, add the following parameters to the start command: 

   -XX:PermSize=256M 
   -XX:MaxPermSize=512M

If the OutOfMemoryError: metaspace error is reported, add the following parameters to the start command: 

   -XX:MetaspaceSize=256M 
   -XX:MaxMetaspaceSize=512M

[Back to Top]

How do I test the network connectivity?

Before you install an ARMS agent, make sure that port 8883, port 8443, and port 8442 can be accessed. You can run the Telnet command to check whether the host on which your application is deployed is connected to the ARMS server. For example, if you want to test the connectivity in the China (Shenzhen) region, log on to the host on which the application is deployed and run the following commands:

telnet arms-dc-sz.aliyuncs.com 8883
telnet arms-dc-sz.aliyuncs.com 8443
telnet arms-dc-sz.aliyuncs.com 8442
Note You can replace the domain name in the preceding commands with the actual endpoint of ARMS Application Monitoring. The endpoint of ARMS Application Monitoring varies in the classic network, the Internet, and virtual private clouds (VPCs).
Table 1. Endpoints of ARMS Application Monitoring
RegionEndpoint for access from the classic network and the InternetEndpoint for access from a VPC
China (Hangzhou)arms-dc-hz.aliyuncs.comarms-dc-hz-internal.aliyuncs.com
China (Shanghai)arms-dc-sh.aliyuncs.comarms-dc-sh-internal.aliyuncs.com
China (Qingdao)arms-dc-qd.aliyuncs.comarms-dc-qd-internal.aliyuncs.com
China (Beijing)arms-dc-bj.aliyuncs.comarms-dc-bj-internal.aliyuncs.com
China (Zhangjiakou)arms-dc-zb.aliyuncs.comarms-dc-zb-internal.aliyuncs.com
China (Hohhot)dc-cn-huhehaote.arms.aliyuncs.comdc-cn-huhehaote-internal.arms.aliyuncs.com
China (Ulanqab)dc-cn-wulanchabu.arms.aliyuncs.comdc-cn-wulanchabu-internal.arms.aliyuncs.com
China (Shenzhen)arms-dc-sz.aliyuncs.comarms-dc-sz-internal.aliyuncs.com
China (Heyuan)dc-cn-heyuan.arms.aliyuncs.comdc-cn-heyuan-internal.arms.aliyuncs.com
China (Guangzhou)dc-cn-guangzhou.arms.aliyuncs.comdc-cn-guangzhou-internal.arms.aliyuncs.com
China (Chengdu)dc-cn-chengdu.arms.aliyuncs.comdc-cn-chengdu-internal.arms.aliyuncs.com
China (Hong Kong)arms-dc-hk.aliyuncs.comarms-dc-hk-internal.aliyuncs.com
Singaporearms-dc-sg.aliyuncs.comarms-dc-sg-internal.aliyuncs.com
Australia (Sydney)dc-ap-southeast-2.arms.aliyuncs.comdc-ap-southeast-2-internal.arms.aliyuncs.com
Malaysia (Kuala Lumpur)dc-ap-southeast-3.arms.aliyuncs.comdc-ap-southeast-3-internal.arms.aliyuncs.com
Indonesia (Jakarta)arms-dc-indonesia.aliyuncs.comarms-dc-indonesia-internal.aliyuncs.com
Japan (Tokyo)arms-dc-jp.aliyuncs.comarms-dc-jp-internal.aliyuncs.com
Germany (Frankfurt)arms-dc-frankfurt.aliyuncs.comarms-dc-frankfurt-internal.aliyuncs.com
UK (London)dc-eu-west-1.arms.aliyuncs.comdc-eu-west-1-internal.arms.aliyuncs.com
US (Virginia)dc-us-east-1.arms.aliyuncs.comdc-us-east-1-internal.arms.aliyuncs.com
US (Silicon Valley)arms-dc-usw.aliyuncs.comdc-us-west-1-internal.arms.aliyuncs.com
India (Mumbai)dc-ap-south-1.arms.aliyuncs.comdc-ap-south-1-internal.arms.aliyuncs.com
Alibaba Gov Cloudarms-dc-gov.aliyuncs.comarms-dc-gov-internal.aliyuncs.com
China East 1 Financearms-dc-hz-finance.aliyuncs.comarms-dc-hz-finance-internal.aliyuncs.com
China East 2 Financearms-dc-sh-finance.aliyuncs.comarms-dc-sh-finance-internal.aliyuncs.com
China South 1 Financearms-dc-sz-finance.aliyuncs.comarms-dc-sz-finance-internal.aliyuncs.com

[Back to Top]

How do I check whether an ARMS agent is installed?

Run the following ps command to check whether an ARMS agent is installed based on the parameters in the start command. 

ps -ef | grep 'arms-bootstrap'

The results shown in the following figure indicates that an ARMS agent is installed.

ARMS Agent

The value of the Darms.licenseKey parameter in the command must be the same as the license key displayed on the Add Application page in the ARMS console.

ARMS Access Application

[Back to Top]

Why is monitoring data not displayed in the ARMS console after I install an ARMS agent?

  1. If the log of the ARMS agent contains send agent metrics. no metrics., check whether your application is continuously accessed by external requests and whether the development framework is supported by the ARMS agent. The external requests include HTTP requests, High-Speed Service Framework (HSF) requests, and Dubbo requests. For more information about third-party components and frameworks supported by an ARMS agent, see Overview.
  2. Check whether the specified time range for query is valid. Set the query time range to the previous 15 minutes and check whether monitoring data is displayed.
  3. If you start the ARMS agent by running the -jar command, check the command configuration and make sure that the -javaagent parameter is specified before -jar. The following sample code provides an example on how to add parameters to the start command: 
    java -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey=xxx -Darms.appName=xxx -jar demoApp.jar
  4. If the logs stored in ArmsAgent/log/ include the "LicenseKey is invalid." error, check whether the region to which the application belongs is consistent with the region to which the agent belongs.
  5. After your application is started, if the log folder does not exist in the ArmsAgent folder, the arms-bootstrap-1.7.0-SNAPSHOT.jar package fails to be loaded. Check whether you are granted the required permissions on the ArmsAgent folder.

  6. If the following error is reported when your application is started, check whether the arms-bootstrap-1.7.0-SNAPSHOT.jar package and the corresponding permissions are valid. 

    Error opening zip file or JAR manifest missing: /root/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar
Error occurred during initialization of VM
agent library failed to init: instrument
  7. If monitoring data is not displayed, compress the logs of the ARMS agent for Java applications in the ArmsAgent/log directory into a compressed file, and contact the DingTalk account arms160804 to obtain technical support.

  8. Check the Java Development Kit (JDK) version. If the JDK version is 1.8.0_25 or 1.8.0_31, the agent may fail to be installed. We recommend that you update the JDK or contact the DingTalk account arms160804.

[Back to Top]

What do I do if no IP address or an invalid IP address is displayed after an ARMS agent is installed?

  1. Run the ifconfig -a command to check the network configuration of the current host. If the host uses multiple network interface controllers (NICs), the IP address obtained by the ARMS agent may be inconsistent with the actual IP address due to network configurations.
  2. You can resolve the error by using one of the following methods:
    • Configure the -DEAGLEEYE.LOCAL.IP=10.XX.XX.XX parameter of the JVM.
      Note Replace 10.XX.XX.XX with the actual IP address.
    • Configure the ARMS agent to obtain the value of the -DNETWORK.INTERFACE=eth0 parameter, in which eth0 indicates the NIC name.

[Back to Top]

How do I troubleshoot errors included in the logs of the ARMS agent that are stored in the ArmsAgent/log directory?

If the "LicenseKey is invalid" error is included in the logs, perform the following operations to troubleshoot the error:

  1. Make sure that the application is created in ARMS and the license key that you specified when an ARMS agent is installed is valid.
  2. ARMS supports multiple regions. Therefore, check whether the download URL of the ARMS agent is in the same region as your application.

[Back to Top]

How do I deploy multiple instances on a single host?

To deploy multiple instances of an application on a single host, set the -Darms.agentId parameter to specify the JVM process to connect to. This parameter indicates a logical number such as 001 and 002. The following command provides an example on how to deploy multiple instances on a single host:

java -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey=<LicenseKey> -Darms.appName=<AppName> -Darms.agentId=001 -jar demoApp.jar

[Back to Top]

What do I do if an ARMS agent cannot be installed?

  1. Make sure that your ECS instance can access the download URL of the ARMS agent over the Internet in the region in which the ECS instance is located.
    RegionDownload URL over the Internet
    China (Hangzhou)arms-apm-cn-hangzhou.oss-cn-hangzhou.aliyuncs.com/ArmsAgent.zip
    China (Shanghai)arms-apm-cn-shanghai.oss-cn-shanghai.aliyuncs.com/ArmsAgent.zip
    China (Qingdao)arms-apm-cn-qingdao.oss-cn-qingdao.aliyuncs.com/ArmsAgent.zip
    China (Beijing)arms-apm-cn-beijing.oss-cn-beijing.aliyuncs.com/ArmsAgent.zip
    China (Zhangjiakou)arms-apm-cn-zhangjiakou.oss-cn-zhangjiakou.aliyuncs.com/ArmsAgent.zip
    China (Hohhot)arms-apm-cn-huhehaote.oss-cn-huhehaote.aliyuncs.com/ArmsAgent.zip
    China (Ulanqab)arms-apm-cn-wulanchabu.oss-cn-wulanchabu.aliyuncs.com/ArmsAgent.zip
    China (Shenzhen)arms-apm-cn-shenzhen.oss-cn-shenzhen.aliyuncs.com/ArmsAgent.zip
    China (Heyuan)arms-apm-cn-heyuan.oss-cn-heyuan.aliyuncs.com/ArmsAgent.zip
    China (Guangzhou)arms-apm-cn-guangzhou.oss-cn-guangzhou.aliyuncs.com/ArmsAgent.zip
    China (Chengdu)arms-apm-cn-chengdu.oss-cn-chengdu.aliyuncs.com/ArmsAgent.zip
    China (Hong Kong)arms-apm-cn-hongkong.oss-cn-hongkong.aliyuncs.com/ArmsAgent.zip
    Singaporearms-apm-ap-southeast-1.oss-ap-southeast-1.aliyuncs.com/ArmsAgent.zip
    Australia (Sydney)arms-apm-ap-southeast-2.oss-ap-southeast-2.aliyuncs.com/ArmsAgent.zip
    Malaysia (Kuala Lumpur)arms-apm-ap-southeast-3.oss-ap-southeast-3.aliyuncs.com/ArmsAgent.zip
    Indonesia (Jakarta)arms-apm-ap-southeast-5.oss-ap-southeast-5.aliyuncs.com/ArmsAgent.zip
    Japan (Tokyo)arms-apm-ap-northeast-1.oss-ap-northeast-1.aliyuncs.com/ArmsAgent.zip
    Germany (Frankfurt)arms-apm-eu-central-1.oss-eu-central-1.aliyuncs.com/ArmsAgent.zip
    UK (London)arms-apm-eu-west-1.oss-eu-west-1.aliyuncs.com/ArmsAgent.zip
    US (Virginia)arms-apm-us-east-1.oss-us-east-1.aliyuncs.com/ArmsAgent.zip
    US (Silicon Valley)arms-apm-us-west-1.oss-us-west-1.aliyuncs.com/ArmsAgent.zip
    India (Mumbai)arms-apm-ap-south-1.oss-ap-south-1.aliyuncs.com/ArmsAgent.zip
    Alibaba Gov Cloudarms-apm-cn-north-2-gov-1.oss-cn-north-2-gov-1.aliyuncs.com/ArmsAgent.zip
  2. Make sure that your ECS instance can access the ARMS console.
  3. Log on to the ECS console and perform the following steps:
    1. In the left-side navigation pane, choose Maintenance & Monitoring > ECS Cloud Assistant.
    2. On the Cloud Assistant page, click the Commands tab, click the search box and select Command Name, enter InstallJavaAgent, and then press the Enter key.
      Commands on the Cloud Assistant page
      Note If no result is returned for the search, contact the DingTalk account arms160804 to obtain technical support.
    3. On the Cloud Assistant page, click the Command Execution Result tab and enter the task ID of the InstallJavaAgent command in the search box. In the search results, click View in the Actions column of this command and check whether this command is run. If the command fails to run, troubleshoot the errors based on the execution results. For example, if this issue occurs because the disk of the ECS instance is full or an ARMS agent is not installed, clear the disk or install an ARMS agent. If this error is not resolved, send the execution results to the DingTalk account arms160804 to obtain technical support.

[Back to Top]

What do I do if the information about the processes of the ECS instance is inaccurate after an ARMS agent is installed?

If the information about the processes of the ECS instance is not displayed or the information is inaccurate after an ARMS agent is installed, click the - icon on the left side of the ECS instance and click the + icon to refresh the data. If the error is not resolved, contact the DingTalk account arms160804 to obtain technical support.

[Back to Top]

What do I do if I cannot enable ARMS application monitoring for a process on an ECS instance?

Check whether the /root/.arms/supervisor/logs/arms-supervisor.log file of the ECS instance contains errors. If the log file contains errors, troubleshoot the error based on the error message. If the error is not resolved, contact the DingTalk account arms160804 to obtain technical support.

[Back to Top]

Why is application monitoring data not displayed after an ARMS agent is installed on a Java application of JDK 11 in an ACK cluster?

Possible cause: The JDK version parameter is not added to the YAML file of the application.

Solution: Perform the following steps to add the JDK version parameter to the YAML file of the application.

  1. Log on to the ACK console.
  2. In the left-side navigation pane, click Clusters. On the Clusters page, find the ACK cluster in which the Java application is deployed and click Applications in the Actions column.
  3. At the top of the Deployments page, select the namespace where your application resides, find the application, and then choose More > View in YAML in the Actions column.
  4. In the Edit YAML dialog box, go to the spec -> template -> metadata -> labels section and append the following content: 
    one-agent.jdk.version: "OpenJDK11"
    Edit YAML

[Back to Top]

Why is application monitoring data not displayed after an ARMS agent is installed on a Java application in an ACK cluster?

  1. Log on to the ACK console.
  2. In the left-side navigation pane, click Clusters. On the Clusters page, find the ACK cluster in which the Java application is deployed and click Applications in the Actions column.
  3. In the left-side navigation pane, click Pods. On the Pods page, select the namespace in which your application resides, find the application, and then click Edit in the Actions column.
  4. In the Edit YAML dialog box, check whether the YAML file contains initContainers.
    db_am_ack_apppod_yaml
    • If the YAML file does not contain initContainers, the pod has not been injected into arms-init-container. Perform Step 5.
    • If the YAML file contains initContainers, the pod has been injected into arms-init-container. Perform Step 8.
  5. At the top of the Pods page, select the ack-onepilot namespace. Check whether a pod whose name is prefixed with ack-onepilot exists in the pod list.
  6. On the Deployments or StatefulSets page, click More in the Actions column and select View in YAML. In the Edit YAML dialog box, check whether the YAML file contains the following labels: 
    labels:
  armsPilotAutoEnable: "on"
  armsPilotCreateAppName: "<your-deployment-name>" // Replace <your-deployment-name> with the actual application name. 
  one-agent.jdk.version: "OpenJDK11" // If the application uses JDK 11, you must configure this parameter.
    • If the YAML file contains the labels, perform Step 7.
    • If the YAML file does not contain the labels, perform the following operations: In the Edit YAML dialog box, add the labels to the spec > template > metadata section and replace <your-deployment-name> with the actual application name. Then, click Update.
  7. On the Pods page, find the pod where your application resides and click Logs in the Actions column to check whether the pod logs of ack-onepilot report a Security Token Service (STS) error in the "Message":"STS error" format.
  8. On the Pods page, find the pod where your application resides and click Edit in the Actions column. In the Edit YAML dialog box, check whether the YAML file contains the following javaagent parameter: 
    -javaagent:/home/admin/.opt/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar
    • If the YAML file contains the parameter, find the pod of the application on the Pods page and click Terminal in the Actions column to go to the command line page. Run the following command to check whether the logs file contains a log file with the .log file extension. Then, contact the DingTalk account arms160804. 
      cd /home/admin/.opt/ArmsAgent/logs
    • If the YAML file does not contain the parameter, contact the DingTalk account arms160804 to obtain technical support.

[Back to Top]

Why does an ARMS agent fail to be installed for an application in an ACK cluster?

Possible cause: ARMS Addon Token is not enabled for the ACK cluster.

Solution:

How do I check whether ARMS Addon Token exists in a cluster?

  1. Log on to the ACK console. In the left-side navigation pane, click Clusters. On the Clusters page, click the name of the cluster to go to the cluster details page.
  2. In the left-side navigation pane, choose Configurations > Secrets.
  3. In the upper part of the page, select kube-system from the Namespace drop-down list and check whether addon.arms.token displays on the Secrets page.
    ARMS Addon Token

Solution: Grant ACK the permissions to access ARMS.

  1. Log on to the ACK console.
  2. In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster in which your application is deployed and click Details in the Actions column.
    Manage Cluster
  3. On the details page of the cluster, click the Cluster Resources tab. On the Cluster Resources tab, click the hyperlink next to Worker RAM Role.
    Worker RAM Link
  4. You are redirected to the RAM Roles page in the RAM console. On the RAM Roles page, click the policy name on the Permissions tab.
  5. On the Policy Document tab, click Modify Policy Document, add the following code in the code editor below Policy Document, and then click OK. 
    {
   "Action": "arms:*",
   "Resource": "*",
   "Effect": "Allow"
}
    Modify RAM Authorization

[Back to Top]

Why is application monitoring data not displayed after an ARMS agent is installed on a Java application of JDK 11 in an open source Kubernetes cluster?

Possible cause: The JDK version parameter is not added to the YAML file of the application.

Solution: In the YAML file, go to the spec -> template -> metadata -> labels section and append the following content: 

one-agent.jdk.version: "OpenJDK11"

[Back to Top]

How do I report ACK cluster data across regions?

  1. In the Deployment in the arms-pilot namespace of the ACK cluster, add the ARMS_REPORT_REGION environment variable. The value must be the ID of a region where ARMS is available. For example, you can set the value to cn-hangzhou or cn-beijing.
  2. Restart the existing application or deploy a new application to report data across regions.
    Note After the environment variable is added, all applications that are deployed in the cluster report data to the specified region.

What do I do if an application cannot be started?

Run the following command to view ack-onepilot logs and troubleshoot the error based on the logs: 

k logs -f ack-onepilot-ack-onepilot-XXXX-XXXX -n ack-onepilot
Note XXXX-XXXX specifies random information. You can obtain the information by running the k get pod -n ack-onepilot command.

[Back to Top]

How do I view the logs of an ARMS agent?

On the worker of the ACK cluster, view the /home/admin/.opt/ArmsAgent/logs/xxxx.log file.

[Back to Top]

How do I change the name of a common Java application on which an ARMS agent is manually installed?

Common Java applications refer to the Java applications that are not deployed on ECS instances. If you install the ARMS agent on the application, you are required to specify the directory of the agent during the installation.

You can view the version file in the directory of the ARMS agent to check the version of the agent. For example, 2.5.8_cf020486_20190816150025 indicates that the version of the ARMS agent is 2.5.8 and is released on August 16, 2019.

  1. Run one of the following commands to download and extract Supervisor over the Internet or a VPC.
    Note Replace the download URL in the commands with the URL for the region in which the Java application resides.
    • Download URL over the Internet 
      wget http://arms-apm-hangzhou.oss-cn-hangzhou.aliyuncs.com/ArmsSupervisor.zip -O ArmsSupervisor.zip
unzip ArmsSupervisor.zip
    • Download URL from a VPC (when the download URL over the Internet is unavailable) 
      wget http://arms-apm-hangzhou.oss-cn-hangzhou-internal.aliyuncs.com/ArmsSupervisor.zip -O ArmsSupervisor.zip
unzip ArmsSupervisor.zip
  2. Run the following command to change the name of the Java application: 
    cd ArmsSupervisor
./attach.sh </path/to/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar> <PID> <NewAppName> <LicenseKey>
    • </path/to/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar>: the path of the arms-bootstrap-1.7.0-SNAPSHOT.jar file.
    • <PID>: the process identifier (PID) of the application. You can run the jps/ps command to obtain the PID.
    • <NewAppName>: the new application name.
    • <LicenseKey>: the license key of the application monitored by ARMS. You can obtain the license key in the ARMS console.

If the standard output shown in the following figure is displayed, the application name is changed.

Name Change Success

[Back to Top]

How do I change the name of a Java application deployed in an ACK cluster?

You can view the version file in the directory of the ARMS agent to check the version of the agent. For example, 2.5.8_cf020486_20190816150025 indicates that the version of the ARMS agent is 2.5.8 and is released on August 16, 2019.

Change the value of the armsPilotCreateAppName parameter in the Deployment and restart the pod.

Wait until your application name is changed. Monitoring data of the application is reported by using the new name rather than the previous name.

[Back to Top]

How do I change the name of a Java application deployed in EDAS?

The names of Java applications deployed in Enterprise Distributed Application Service (EDAS) cannot be changed.

[Back to Top]

How do I uninstall an ARMS agent that is manually installed?

For more information about how to manually install an ARMS agent on Java applications, see Manually install an ARMS agent for a Java application. You can perform the following steps to uninstall an ARMS agent that is manually installed:

  1. If you no longer want to use ARMS to monitor your Java applications, delete all parametersrelated to AppName and LicenseKey, which are described in Step 8.
  2. Restart the Java application.

[Back to Top]

How do I uninstall an ARMS agent that is installed on a Java application deployed on an ECS instance?

  1. If you no longer want to use ARMS to monitor your Java applications, run the jps -l command to view all processes and obtain the PID of com.alibaba.mw.arms.apm.supervisor.daemon.Daemon in the returned results.
    In this example, the PID of com.alibaba.mw.arms.apm.supervisor.daemon.Daemon is 62857. Kill Process
  2. Run the kill -9 <PID> command.
    Example: kill -9 62857.
  3. Run the rm -rf /.arms /root/.arms command.
  4. Restart your application.

[Back to Top]

How do I uninstall an ARMS agent that is installed on a Java application deployed in an ACK cluster?

If you no longer want to use ARMS to monitor a Java application deployed in an ACK cluster, perform the following steps to uninstall the ARMS agent:

  1. Log on to the ACK console.
  2. In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that contains the Java application from which you want to uninstall the ARMS agent and click Applications in the Actions column.
  3. In the left-side navigation pane, choose Applications > Helm.
  4. On the Helm page, find the release named arms-pilot of the ARMS agent, and click Delete in the Actions column.
  5. In the Delete message, click OK.
  6. Restart the pod of your service.

[Back to Top]

How do I uninstall an ARMS agent that is installed on a Java application deployed in an open source Kubernetes environment?

  1. If you no longer want to use ARMS to monitor your Java applications deployed in an open-source Kubernetes environment, run the following command to uninstall arms-pilot: 
    helm del --purge arms-pilot
  2. Restart the pod of your service.

[Back to Top]

How do I uninstall an ARMS agent that is installed on a Java application deployed in a Docker cluster?

  1. If you no longer want to use ARMS to monitor a Java application deployed in a Docker cluster, delete the content of the Dockerfile that you modified in Step 1 in the Install the ARMS agent for a Java application deployed in a Docker cluster topic.
  2. Run the docker build command to build an image.
  3. Run the docker run command to run the image.

[Back to Top]

How do I uninstall an ARMS agent that is installed on a PHP application?

If you no longer want to use ARMS to monitor a PHP application that is not deployed in an ACK cluster, perform the following steps to uninstall the ARMS agent:

  1. Delete the following lines from the php.ini file:
    [arms] 
extension=<php_extension_dir>/arms.so
arms.trace_exception=true
arms.config_full_name=/<php-agent-dir>/arms-agent.conf
  2. Restart your PHP application.

[Back to Top]

How do I uninstall an ARMS agent that is installed on a PHP application deployed in an ACK cluster?

If you no longer want to use ARMS to monitor a PHP application deployed in an ACK cluster, perform the following steps to uninstall the ARMS agent:

  1. Log on to the ACK console.
  2. In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that contains the Java application from which you want to uninstall the ARMS agent and click Applications in the Actions column.
  3. In the left-side navigation pane, choose Applications > Helm.
  4. On the Helm page, find the release named arms-pilot of the ARMS agent, and click Delete in the Actions column.
  5. In the Delete message, click OK.
  6. Restart the pod of your service.

[Back to Top]

Why is the data of my application that uses the OpenFeign component incomplete in ARMS?

After your application that uses the OpenFeign component is connected to ARMS application monitoring, the application data may be incomplete and the data of downstream applications may fail to be displayed. By default, the OpenFeign component enables Hystrix that uses the RxJava asynchronous framework. This issue may occur due to the preceding reason. ARMS does not support asynchronous frameworks.

Note This description applies to scenarios in which the version of the ARMS agent for Java applications is earlier than 2.6.0. The ARMS agent of version 2.6.0 or later that is provided for Java applications supports asynchronous frameworks.

You can disable Hystrix and enable the OkHttp request class to resolve this issue.

  1. Add the following dependency to the pom.xml file: 
    <!-- OKHttp supports Feign -->
<dependency>
    <groupId>io.github.openfeign</groupId>
    <artifactId>feign-okhttp</artifactId>
</dependency>
  2. Add the following content to the SpringCloud configuration file: 
    feign.okhttp.enabled: true
feign.hystrix.enabled: false
  3. Configure the OkHttp request class: 
    @Configuration
@ConditionalOnClass(Feign.class)
@AutoConfigureBefore(FeignAutoConfiguration.class)
public class FeignClientOkHttpConfiguration {

    @Bean
    public OkHttpClient okHttpClient() {
        return new OkHttpClient.Builder()
                // The connection times out.
                .connectTimeout(20, TimeUnit.SECONDS)
                // The response times out.
                .readTimeout(20, TimeUnit.SECONDS)
                // The write request times out.
                .writeTimeout(20, TimeUnit.SECONDS)
                // Indicates whether to enable automatic reconnection.
                .retryOnConnectionFailure(true)
                // The connection pool.
                .connectionPool(new ConnectionPool())
                .build();
    }

[Back to Top]