Agen Application Real-Time Monitoring Service (ARMS) harus mempertahankan konektivitas jaringan ke sisi server agar berfungsi dengan baik. Topik ini menjelaskan persyaratan jaringan untuk pelaporan data di ruang kerja Cloud Monitor default dan non-default, serta cara memeriksa konektivitas jaringan.
Persyaratan konektivitas jaringan untuk ruang kerja Cloud Monitor default
Ruang kerja Cloud Monitor default menggunakan tautan pelaporan data ARMS asli.
Port yang harus dibuka
Port | Deskripsi |
80 | Disediakan oleh titik akhir trace dan metadata, titik akhir metrik, layanan continuous profiling, dan layanan self-monitoring agen untuk pelaporan data. |
8080 | Disediakan oleh layanan ACM untuk konfigurasi aplikasi. |
8848 | Disediakan oleh layanan ACM untuk konfigurasi aplikasi. |
9990 | Disediakan oleh titik akhir trace dan metadata untuk pelaporan metadata. |
9092 | Disediakan oleh titik akhir trace dan metadata untuk diagnostik aplikasi. |
9093 | Disediakan oleh titik akhir trace dan metadata untuk keamanan aplikasi. |
Domain yang harus dibuka
Jika aplikasi Anda diterapkan di Virtual Private Cloud (VPC), termasuk skenario di mana data center on-premises Anda terhubung ke VPC melalui Express Connect, gunakan Titik akhir pribadi secara preferensial. Jika aplikasi Anda diterapkan di data center on-premises atau cloud lain, gunakan Titik akhir publik.
Wilayah | Titik akhir publik | Titik akhir pribadi (VPC) |
China (Hangzhou) | arms-dc-hz.aliyuncs.com (trace dan metadata) | arms-dc-hz-internal.aliyuncs.com (trace dan metadata) |
China (Shanghai) | arms-dc-sh.aliyuncs.com (trace dan metadata) | arms-dc-sh-internal.aliyuncs.com (trace dan metadata) |
China (Qingdao) | arms-dc-qd.aliyuncs.com (trace dan metadata) | arms-dc-qd-internal.aliyuncs.com (trace dan metadata) |
China (Beijing) | arms-dc-bj.aliyuncs.com (trace dan metadata) | arms-dc-bj-internal.aliyuncs.com (trace dan metadata) |
China (Zhangjiakou) | arms-dc-zb.aliyuncs.com (trace dan metadata) | arms-dc-zb-internal.aliyuncs.com (trace dan metadata) |
China (Hohhot) | dc-cn-huhehaote.arms.aliyuncs.com (trace dan metadata) | dc-cn-huhehaote-internal.arms.aliyuncs.com (trace dan metadata) |
China (Ulanqab) | dc-cn-wulanchabu.arms.aliyuncs.com (trace dan metadata) | dc-cn-wulanchabu-internal.arms.aliyuncs.com (trace dan metadata) |
China (Shenzhen) | arms-dc-sz.aliyuncs.com (trace dan metadata) | arms-dc-sz-internal.aliyuncs.com (trace dan metadata) |
China (Heyuan) | dc-cn-heyuan.arms.aliyuncs.com (trace dan metadata) | dc-cn-heyuan-internal.arms.aliyuncs.com (trace dan metadata) |
China (Guangzhou) | dc-cn-guangzhou.arms.aliyuncs.com (trace dan metadata) | dc-cn-guangzhou-internal.arms.aliyuncs.com (trace dan metadata) |
China (Chengdu) | dc-cn-chengdu.arms.aliyuncs.com (trace dan metadata) | dc-cn-chengdu-internal.arms.aliyuncs.com (trace dan metadata) |
China (Hong Kong) | arms-dc-hk.aliyuncs.com (trace dan metadata) | arms-dc-hk-internal.aliyuncs.com (jejak dan metadata) |
Jepang (Tokyo) | arms-dc-jp.aliyuncs.com (trace dan metadata) | arms-dc-jp-internal.aliyuncs.com (trace dan metadata) |
Singapura | arms-dc-sg.aliyuncs.com (trace dan metadata) | arms-dc-sg-internal.aliyuncs.com (trace dan metadata) |
Malaysia (Kuala Lumpur) | dc-ap-southeast-3.arms.aliyuncs.com (trace dan metadata) | dc-ap-southeast-3-internal.arms.aliyuncs.com (trace dan metadata) |
Indonesia (Jakarta) | arms-dc-indonesia.aliyuncs.com (trace dan metadata) | arms-dc-indonesia-internal.aliyuncs.com (trace dan metadata) |
Jerman (Frankfurt) | arms-dc-frankfurt.aliyuncs.com (trace dan metadata) | arms-dc-frankfurt-internal.aliyuncs.com (trace dan metadata) |
Inggris (London) | dc-eu-west-1.arms.aliyuncs.com (trace dan metadata) | dc-eu-west-1-internal.arms.aliyuncs.com (trace dan metadata) |
AS (Virginia) | dc-us-east-1.arms.aliyuncs.com (trace dan metadata) | dc-us-east-1-internal.arms.aliyuncs.com (trace dan metadata) |
AS (Silicon Valley) | arms-dc-usw.aliyuncs.com (trace dan metadata) | dc-us-west-1-internal.arms.aliyuncs.com (trace dan metadata) |
Secara default, agen secara otomatis mendeteksi jaringan dan menggunakan Titik akhir pribadi terlebih dahulu; jika Titik akhir pribadi tidak dapat dijangkau, agen akan beralih ke Titik akhir publik.
Rentang IP yang harus dibuka
Jika aplikasi Anda diterapkan di VPC, setelah memastikan bahwa nama domain pribadi dapat dijangkau, buka rentang IP internal untuk setiap layanan. Titik akhir publik tidak memiliki rentang IP tetap; konfigurasikan kebijakan jaringan Anda berdasarkan nama domain.
Alamat IP mesin ACM yang harus dibuka
Agen terhubung ke mesin ACM untuk mengambil konfigurasi. Anda dapat menanyakan IP mesin untuk wilayah Anda menggunakan domain ACM:
curl 'http://acm.aliyun.com:8080/diamond-server/diamond'Pastikan firewall Anda mengizinkan akses ke alamat IP mesin ACM yang dikembalikan.
Persyaratan konektivitas jaringan untuk ruang kerja Cloud Monitor non-default
Ruang kerja Cloud Monitor non-default menggunakan tautan pelaporan data Simple Log Service (SLS). Secara default, tautan ini menggunakan protokol HTTP, jaringan IPv4, dan port 80. Jika aplikasi dan ruang kerja target berada di wilayah Alibaba Cloud yang sama, disarankan untuk menggunakan Titik akhir layanan pribadi; jika tidak, gunakan Titik akhir layanan publik.
Saat menggunakan Titik akhir pribadi SLS di cloud publik, Anda harus menggunakan alamat DNS pribadi Alibaba Cloud 100.100.2.136 dan 100.100.2.138; jika tidak, alamat IP virtual pribadi (VIP) mungkin tidak terselesaikan dengan benar.
Titik akhir layanan cloud publik
Wilayah | Titik akhir layanan publik | Titik akhir layanan pribadi |
China (Hangzhou) | cn-hangzhou.log.aliyuncs.com | cn-hangzhou-intranet.log.aliyuncs.com |
China (Shanghai) | cn-shanghai.log.aliyuncs.com | cn-shanghai-intranet.log.aliyuncs.com |
China (Nanjing) (wilayah lokal, sedang dihentikan) | cn-nanjing.log.aliyuncs.com | cn-nanjing-intranet.log.aliyuncs.com |
China (Fuzhou) (wilayah lokal, sedang dihentikan) | cn-fuzhou.log.aliyuncs.com | cn-fuzhou-intranet.log.aliyuncs.com |
China (Qingdao) | cn-qingdao.log.aliyuncs.com | cn-qingdao-intranet.log.aliyuncs.com |
China (Beijing) | cn-beijing.log.aliyuncs.com | cn-beijing-intranet.log.aliyuncs.com |
China (Zhangjiakou) | cn-zhangjiakou.log.aliyuncs.com | cn-zhangjiakou-intranet.log.aliyuncs.com |
China (Hohhot) | cn-huhehaote.log.aliyuncs.com | cn-huhehaote-intranet.log.aliyuncs.com |
China (Ulanqab) | cn-wulanchabu.log.aliyuncs.com | cn-wulanchabu-intranet.log.aliyuncs.com |
China (Shenzhen) | cn-shenzhen.log.aliyuncs.com | cn-shenzhen-intranet.log.aliyuncs.com |
China (Heyuan) | cn-heyuan.log.aliyuncs.com | cn-heyuan-intranet.log.aliyuncs.com |
China (Guangzhou) | cn-guangzhou.log.aliyuncs.com | cn-guangzhou-intranet.log.aliyuncs.com |
China (Chengdu) | cn-chengdu.log.aliyuncs.com | cn-chengdu-intranet.log.aliyuncs.com |
China (Hong Kong) | cn-hongkong.log.aliyuncs.com | cn-hongkong-intranet.log.aliyuncs.com |
Jepang (Tokyo) | ap-northeast-1.log.aliyuncs.com | ap-northeast-1-intranet.log.aliyuncs.com |
Korea Selatan (Seoul) | ap-northeast-2.log.aliyuncs.com | ap-northeast-2-intranet.log.aliyuncs.com |
Singapura | ap-southeast-1.log.aliyuncs.com | ap-southeast-1-intranet.log.aliyuncs.com |
Malaysia (Kuala Lumpur) | ap-southeast-3.log.aliyuncs.com | ap-southeast-3-intranet.log.aliyuncs.com |
Indonesia (Jakarta) | ap-southeast-5.log.aliyuncs.com | ap-southeast-5-intranet.log.aliyuncs.com |
Filipina (Manila) | ap-southeast-6.log.aliyuncs.com | ap-southeast-6-intranet.log.aliyuncs.com |
Thailand (Bangkok) | ap-southeast-7.log.aliyuncs.com | ap-southeast-7-intranet.log.aliyuncs.com |
UEA (Dubai) | me-east-1.log.aliyuncs.com | me-east-1-intranet.log.aliyuncs.com |
Jerman (Frankfurt) | eu-central-1.log.aliyuncs.com | eu-central-1-intranet.log.aliyuncs.com |
Inggris (London) | eu-west-1.log.aliyuncs.com | eu-west-1-intranet.log.aliyuncs.com |
AS (Virginia) | us-east-1.log.aliyuncs.com | us-east-1-intranet.log.aliyuncs.com |
AS (Silicon Valley) | us-west-1.log.aliyuncs.com | us-west-1-intranet.log.aliyuncs.com |
Untuk informasi lebih lanjut mengenai Titik akhir layanan, lihat Titik akhir layanan untuk jenis jaringan berbeda di Simple Log Service.
Periksa konektivitas jaringan secara otomatis
Prasyarat
Instal curl dan nc pada kontainer atau mesin tempat aplikasi Anda berjalan. Skrip ini menggunakan curl -4 untuk memaksa permintaan HTTP IPv4, dengan timeout koneksi 1 detik untuk semua pemeriksaan.
Jalankan skrip pemeriksaan otomatis
Buat
check_network.shdan tambahkan konten berikut:#!/usr/bin/env bash set -u TIMEOUT_SECONDS=1 REGION_ID="${1:-}" if ! command -v curl >/dev/null 2>&1; then echo "curl is not installed. Please install it from: https://curl.se/" exit 1 fi if ! command -v nc >/dev/null 2>&1; then echo "nc is not installed. Please install it from: https://netcat.sourceforge.net/" exit 1 fi if [ -z "${REGION_ID}" ]; then TOKEN=$(curl -4 -sS --connect-timeout "${TIMEOUT_SECONDS}" --max-time "${TIMEOUT_SECONDS}" -X PUT "http://100.100.100.200/latest/api/token" -H "X-aliyun-ecs-metadata-token-ttl-seconds:300" 2>/dev/null || true) REGION_ID=$(curl -4 -sS --connect-timeout "${TIMEOUT_SECONDS}" --max-time "${TIMEOUT_SECONDS}" -H "X-aliyun-ecs-metadata-token: ${TOKEN}" "http://100.100.100.200/latest/meta-data/region-id" 2>/dev/null || true) fi if [ -z "${REGION_ID}" ]; then echo "Cannot auto-detect region ID. Run: $0 <region_id>" exit 1 fi check_http() { local name="$1" local url="$2" local http_code http_code=$(curl -4 -sS -o /dev/null --connect-timeout "${TIMEOUT_SECONDS}" --max-time "${TIMEOUT_SECONDS}" -w "%{http_code}" "${url}" 2>/dev/null || true) if [ -n "${http_code}" ] && [ "${http_code}" != "000" ]; then printf '%-44s reachable (HTTP %s) ' "${name}" "${http_code}" else printf '%-44s unreachable ' "${name}" fi } check_tcp() { local name="$1" local host="$2" local port="$3" if nc -z -w "${TIMEOUT_SECONDS}" "${host}" "${port}" >/dev/null 2>&1; then printf '%-44s reachable ' "${name}" else printf '%-44s unreachable ' "${name}" fi } get_default_endpoints() { case "$1" in cn-hangzhou) echo "arms-dc-hz.aliyuncs.com|arms-dc-hz-internal.aliyuncs.com|cn-hangzhou.arms.aliyuncs.com|cn-hangzhou-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-hz-internal.edas.aliyun.com" ;; cn-shanghai) echo "arms-dc-sh.aliyuncs.com|arms-dc-sh-internal.aliyuncs.com|cn-shanghai.arms.aliyuncs.com|cn-shanghai-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-sh-internal.edas.aliyun.com" ;; cn-qingdao) echo "arms-dc-qd.aliyuncs.com|arms-dc-qd-internal.aliyuncs.com|cn-qingdao.arms.aliyuncs.com|cn-qingdao-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-qd-internal.edas.aliyun.com" ;; cn-beijing) echo "arms-dc-bj.aliyuncs.com|arms-dc-bj-internal.aliyuncs.com|cn-beijing.arms.aliyuncs.com|cn-beijing-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-bj-internal.edas.aliyun.com" ;; cn-zhangjiakou) echo "arms-dc-zb.aliyuncs.com|arms-dc-zb-internal.aliyuncs.com|cn-zhangjiakou.arms.aliyuncs.com|cn-zhangjiakou-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-cn-zhangjiakou-internal.edas.aliyun.com" ;; cn-huhehaote) echo "dc-cn-huhehaote.arms.aliyuncs.com|dc-cn-huhehaote-internal.arms.aliyuncs.com|cn-huhehaote.arms.aliyuncs.com|cn-huhehaote-intranet.arms.aliyuncs.com|acm.aliyun.com|-" ;; cn-wulanchabu) echo "dc-cn-wulanchabu.arms.aliyuncs.com|dc-cn-wulanchabu-internal.arms.aliyuncs.com|cn-wulanchabu.arms.aliyuncs.com|cn-wulanchabu-intranet.arms.aliyuncs.com|acm.aliyun.com|-" ;; cn-shenzhen) echo "arms-dc-sz.aliyuncs.com|arms-dc-sz-internal.aliyuncs.com|cn-shenzhen.arms.aliyuncs.com|cn-shenzhen-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-sz-internal.edas.aliyun.com" ;; cn-heyuan) echo "dc-cn-heyuan.arms.aliyuncs.com|dc-cn-heyuan-internal.arms.aliyuncs.com|cn-heyuan.arms.aliyuncs.com|cn-heyuan-intranet.arms.aliyuncs.com|acm.aliyun.com|-" ;; cn-guangzhou) echo "dc-cn-guangzhou.arms.aliyuncs.com|dc-cn-guangzhou-internal.arms.aliyuncs.com|cn-guangzhou.arms.aliyuncs.com|cn-guangzhou-intranet.arms.aliyuncs.com|acm.aliyun.com|-" ;; cn-chengdu) echo "dc-cn-chengdu.arms.aliyuncs.com|dc-cn-chengdu-internal.arms.aliyuncs.com|cn-chengdu.arms.aliyuncs.com|cn-chengdu-intranet.arms.aliyuncs.com|acm.aliyun.com|-" ;; cn-hongkong) echo "arms-dc-hk.aliyuncs.com|arms-dc-hk-internal.aliyuncs.com|cn-hongkong.arms.aliyuncs.com|cn-hongkong-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-hk-internal.edas.aliyun.com" ;; ap-northeast-1) echo "arms-dc-jp.aliyuncs.com|arms-dc-jp-internal.aliyuncs.com|ap-northeast-1.arms.aliyuncs.com|ap-northeast-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-ap-northeast-1-internal.edas.aliyun.com" ;; ap-southeast-1) echo "arms-dc-sg.aliyuncs.com|arms-dc-sg-internal.aliyuncs.com|ap-southeast-1.arms.aliyuncs.com|ap-southeast-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-singapore-internal.edas.aliyun.com" ;; ap-southeast-3) echo "dc-ap-southeast-3.arms.aliyuncs.com|dc-ap-southeast-3-internal.arms.aliyuncs.com|ap-southeast-3.arms.aliyuncs.com|ap-southeast-3-intranet.arms.aliyuncs.com|acm.aliyun.com|-" ;; ap-southeast-5) echo "arms-dc-indonesia.aliyuncs.com|arms-dc-indonesia-internal.aliyuncs.com|ap-southeast-5.arms.aliyuncs.com|ap-southeast-5-intranet.arms.aliyuncs.com|acm.aliyun.com|-" ;; eu-central-1) echo "arms-dc-frankfurt.aliyuncs.com|arms-dc-frankfurt-internal.aliyuncs.com|eu-central-1.arms.aliyuncs.com|eu-central-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-eu-central-1-internal.edas.aliyun.com" ;; eu-west-1) echo "dc-eu-west-1.arms.aliyuncs.com|dc-eu-west-1-internal.arms.aliyuncs.com|eu-west-1.arms.aliyuncs.com|eu-west-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-eu-west-1-internal.edas.aliyun.com" ;; us-east-1) echo "dc-us-east-1.arms.aliyuncs.com|dc-us-east-1-internal.arms.aliyuncs.com|us-east-1.arms.aliyuncs.com|us-east-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-us-east-1-internal.edas.aliyun.com" ;; us-west-1) echo "arms-dc-usw.aliyuncs.com|dc-us-west-1-internal.arms.aliyuncs.com|us-west-1.arms.aliyuncs.com|us-west-1-intranet.arms.aliyuncs.com|acm.aliyun.com|arms-dc-usw.aliyuncs.com" ;; cn-north-2-gov-1) echo "arms-dc-gov.aliyuncs.com|arms-dc-gov-internal.aliyuncs.com|cn-north-2-gov-1.arms.aliyuncs.com|cn-north-2-gov-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-cn-north-2-gov-1-internal.edas.aliyun.com" ;; cn-hangzhou-finance) echo "arms-dc-hz-finance.aliyuncs.com|arms-dc-hz-finance-internal.aliyuncs.com|cn-hangzhou-finance.arms.aliyuncs.com|cn-hangzhou-finance-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-hz-internal.jbp.console.aliyun.com" ;; cn-shanghai-finance-1) echo "arms-dc-sh-finance.aliyuncs.com|arms-dc-sh-finance-internal.aliyuncs.com|cn-shanghai-finance-1.arms.aliyuncs.com|cn-shanghai-finance-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-cn-shanghai-finance-1-internal.edas.aliyun.com" ;; cn-shenzhen-finance-1) echo "arms-dc-sz-finance.aliyuncs.com|arms-dc-sz-finance-internal.aliyuncs.com|cn-shenzhen-finance-1.arms.aliyuncs.com|cn-shenzhen-finance-1-intranet.arms.aliyuncs.com|acm.aliyun.com|addr-sz-internal.jbp.console.aliyun.com" ;; *) return 1 ;; esac } echo "Region: ${REGION_ID}" echo echo "Default Cloud Monitor Workspace (original ARMS reporting link)" DEFAULT_ENDPOINTS=$(get_default_endpoints "${REGION_ID}" || true) if [ -n "${DEFAULT_ENDPOINTS}" ]; then IFS='|' read -r TRACE_PUBLIC TRACE_PRIVATE METRIC_PUBLIC METRIC_PRIVATE ACM_PUBLIC ACM_PRIVATE <<EOF ${DEFAULT_ENDPOINTS} EOF check_http "Public trace and metadata endpoint" "http://${TRACE_PUBLIC}/api/checkHealth" check_http "Private trace and metadata endpoint" "http://${TRACE_PRIVATE}/api/checkHealth" check_http "Public metadata endpoint (9990)" "http://${TRACE_PUBLIC}:9990/api/checkHealth" check_http "Private metadata endpoint (9990)" "http://${TRACE_PRIVATE}:9990/api/checkHealth" check_http "Public metrics endpoint" "http://${METRIC_PUBLIC}/health/readiness" check_http "Private metrics endpoint" "http://${METRIC_PRIVATE}/health/readiness" check_http "Public ACM service (8080)" "http://${ACM_PUBLIC}:8080/diamond-server/diamond" if [ "${ACM_PRIVATE}" != "-" ]; then check_http "Private ACM service (8080)" "http://${ACM_PRIVATE}:8080/diamond-server/diamond" else echo "No private ACM service available for this region. Ensure the public ACM endpoint is reachable." fi check_tcp "Public diagnostics port (9092)" "${TRACE_PUBLIC}" 9092 check_tcp "Private diagnostics port (9092)" "${TRACE_PRIVATE}" 9092 check_tcp "Public security port (9093)" "${TRACE_PUBLIC}" 9093 check_tcp "Private security port (9093)" "${TRACE_PRIVATE}" 9093 else echo "No default cloud monitor workspace endpoint configured for this region." fi echo echo "Non-default Cloud Monitor Workspace (SLS reporting link)" check_http "SLS public service endpoint /health" "http://${REGION_ID}.log.aliyuncs.com/health" check_http "SLS private service endpoint /health" "http://${REGION_ID}-intranet.log.aliyuncs.com/health"Tambahkan izin eksekusi dan jalankan skrip:
chmod +x check_network.sh ./check_network.sh ${region_id}${region_id}adalah ID Wilayah tempat ruang kerja berada, misalnyacn-hangzhou. Jika parameter ini tidak diberikan, skrip akan mencoba mengambil ID Wilayah dari metadata instans ECS saat ini.
Skrip ini memeriksa tautan pelaporan ARMS asli untuk ruang kerja Cloud Monitor default, serta Titik akhir layanan publik dan pribadi SLS untuk ruang kerja Cloud Monitor non-default. Setidaknya satu tautan (publik atau pribadi) yang sesuai dengan jaringan penerapan aktual Anda harus dapat dijangkau.