edit-icon download-icon

FAQs about application monitoring access

Last Updated: Apr 11, 2018

This topic introduces typical failures of connecting ARMS application monitoring when creating applications and how to troubleshoot.

Check network connectivity

Run the Telnet command to check if the target host is connected to the ARMS server network.

Server addresses of ARMS Application Monitoring in different regions

Region Server address
Hangzhou arms-dc-hz.aliyuncs.com
Beijing arms-dc-bj.aliyuncs.com
Shanghai arms-dc-sh.aliyuncs.com
Qingdao arms-dc-qd.aliyuncs.com
Shenzhen arms-dc-sz.aliyuncs.com

If you created an application in Shenzhen region of ARMS, then you should test if the Shenzhen region environment is connected to the ARMS server network.

The following result indicates that the network is connected:

  1. telnet arms-dc-sz.aliyuncs.com 8443
  1. Trying 119.23.169.12...
  2. Connected to arms-dc-sz.aliyuncs.com.
  3. Escape character is '^]'.

NOTE: Use different environment addresses for different regions accordingly. The port remains unchanged.

How to check if ArmsAgent is successfully loaded

  1. Run the following ps command to check if ArmsAgent is successfully loaded according to the command line start parameters.

    1. ps -ef | grep 'arms-bootstrap'

    When ArmsAgent is successfully loaded, the result is as follows:

    Agent loaded

  2. Attributes of arms.licenseKey and arms.appId in the command line must match that displayed on the ARMS application setting page.

What if no data is available after the ArmsAgent is loaded?

  1. Verify if your application has continuous external access requests, including HTTP requests, HSF requests, and Dubbo requests.
  2. Check if the selected time range to query is correct. Select the past 15 minutes as the query time range and see if any monitoring data is available.
Thank you! We've received your feedback.