Application Real-Time Monitoring Service:Network requirements for the ARMS agent for Go

Test network connectivity

Run the following commands on the host where your application is deployed. An HTTP 200 response confirms that the endpoint is reachable. Replace the China (Hangzhou) endpoints with the endpoints for your region.

# Test the trace and metadata endpoint on port 80
curl -I -w "%{http_code}" http://arms-dc-hz.aliyuncs.com/api/checkHealth

# Test the trace and metadata endpoint on port 9990
curl -I -w "%{http_code}" http://arms-dc-hz.aliyuncs.com:9990/api/checkHealth

# Test the metric endpoint
curl -I -w "%{http_code}" http://cn-hangzhou.arms.aliyuncs.com/health/readiness

ARMS CIDR blocks

The required CIDR blocks depend on your deployment:

• VPC or Express Connect: Allow outbound traffic to the ARMS internal endpoints listed above and add 100.0.0.0/8 to your allowlist.

• On-premises data center or third-party cloud: Allow outbound traffic to the ARMS public endpoints. Specific public CIDR blocks are not published.

ACM CIDR blocks

The ARMS agent connects to the ACM engine to retrieve its configuration. Query the ACM CIDR blocks by running:

curl 'acm.aliyun.com:8080/diamond-server/diamond'

These CIDR blocks are stable and rarely change. After retrieving them, verify that your firewall allows outbound access:

curl -X GET "http://<acm-ip>:8080/diamond-server/config.co?dataId=com.ali.art.logicregion.flow.control.icbu&group=art-control-service" -i

Replace <acm-ip> with one of the IP addresses returned by the previous command. A successful response confirms that the ACM engine is reachable. If no configuration data is returned, the firewall is blocking access.