Application Real-Time Monitoring Service (ARMS)'s one-click agent installation for Java applications does not require restarting the applications for the installed agent to take effect. The ARMS agent starts monitoring applications once installed, which is suitable for users who are using the ARMS agent for the first time. When a Java application restarts, the ARMS agent is automatically loaded, and the application is automatically connected to ARMS application monitoring.


  • Ports 8442, 8443, and 8883 in the security group of your server have enabled outbound access on the public network over TCP. This operation is not required within a Virtual Private Cloud (VPC). For more information on how to enable the outbound access for Alibaba Cloud Elastic Compute Service (ECS) instances, see Add security group rules.
    Note In addition to applications on Alibaba Cloud ECS instances, applications on public network servers can also access ARMS.
  • Make sure the third-party components or frameworks that your application uses are supported by ARMS. For more information about the compatibility list, see Supported components and frameworks.
  • If your application is manually connected to ARMS application monitoring, you need to uninstall the ARMS agent before you can use the one-click method. For more information, see Uninstall the ARMS agent.


  1. Log on to the ARMS console. In the left-side navigation pane, choose Application Monitoring > Applications.
  2. On the Applications page, click Create Application in the upper-right corner.
  3. On the Create Application page, select Java, Default Environment, and One-Click Access. Then view and save the LicenseKey.
    Access the agent
  4. Run the installation script corresponding to your region.
    # China (Hangzhou)
    wget -O- | sh && ~/.arms/supervisor/ <licenseKey> Java-Demo
    # China (Shanghai)
    wget -O- | sh && ~/.arms/supervisor/ <licenseKey> Java-Demo
    # China (Qingdao)
    wget -O- | sh && ~/.arms/supervisor/ <licenseKey> Java-Demo
    # China (Beijing)
    wget -O- | sh && ~/.arms/supervisor/ <licenseKey> Java-Demo
    # China (Shenzhen)
    wget -O- | sh && ~/.arms/supervisor/ <licenseKey> Java-Demo
    # Singapore
    wget -O- | sh && ~/.arms/supervisor/ <licenseKey> Java-Demo
    # Finance Cloud
    wget -O- | sh && ~/.arms/supervisor/ <licenseKey> Java-Demo
    • Replace <licenseKey> with your LicenseKey.
    • Replace Java-Demo with the name of your application. Chinese characters currently cannot be used in application names.
    • After the installation script is run, it automatically downloads the latest ARMS agent.
    • If your server has only one Java process, the installation script installs the ARMS agent for this process by default. If your server has multiple Java processes, select a process to install the ARMS agent.


After about one minute, if your application is displayed in the application list and has data reported, it is connected to ARMS.

Uninstall the ARMS agent

  1. If you no longer need ARMS to monitor your Java application, you can run the jps -l command to view all processes and find the process ID of in the command output.
    In this example, the process ID of is 62857.
    Kill process
  2. Run the kill -9 <process ID> command, for example, kill -9 62857.
  3. Run the rm -rf /.arms /root/.arms command.
  4. Restart your application.

Change the name of an application in one click

If you want to change the name of an application, such as if you forget to change the name of the sample application Java-Demo to a custom name, you can change the application name without restarting the application or reinstalling the agent.


  1. How do I handle the following getcwd errors when running the one-click ARMS agent installation script?

    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory Error occurred during initialization of VM java.lang.Error: Properties init: Could not determine current working directory. at java.lang.System.initProperties(Native Method) at java.lang.System.initializeSystemClass(

    The possible cause is that the current directory was deleted by mistake when the script ran. To solve this problem, run cd and then run the script again.

  2. Where do I view the log when installing the ARMS agent with one click?

    The default directory of the log is /root/.arms/supervisor/logs/arms-supervisor.log. If no logs are available in this directory, run ps -ef |grep arms to view the directory where the logs are stored.