O agente do Application Real-Time Monitoring Service (ARMS) requer conectividade de rede com o servidor para funcionar corretamente. Este tópico descreve os requisitos de rede para envio de dados nos workspaces padrão e não padrão do Cloud Monitor e como verificar essa conectividade.
Requisitos de conectividade de rede para o workspace padrão do Cloud Monitor
O workspace padrão do Cloud Monitor usa o link original de envio de dados do ARMS.
Portas a liberar
|
Porta |
Descrição |
|
80 |
Usada pelo endpoint de rastreamento e metadados, endpoint de métricas, service de profiling contínuo e service de automonitoramento do agente para envio de dados. |
|
8080 |
Usada pelo service ACM para configuração de aplicações. |
|
8848 |
Usada pelo service ACM para configuração de aplicações. |
|
9990 |
Usada pelo endpoint de rastreamento e metadados para envio de metadados. |
|
9092 |
Usada pelo endpoint de rastreamento e metadados para diagnósticos da aplicação. |
|
9093 |
Usada pelo endpoint de rastreamento e metadados para segurança da aplicação. |
Domínios a liberar
Se sua aplicação estiver implantada em uma Virtual Private Cloud (VPC), inclusive em cenários onde o data center local se conecta a uma VPC via Express Connect, use preferencialmente o endpoint privado. Caso a aplicação esteja em um data center local ou em outra cloud, use o endpoint público.
|
Região |
Endpoint público |
Endpoint privado (VPC) |
|
China (Hangzhou) |
arms-dc-hz.aliyuncs.com (trace and metadata)cn-hangzhou.arms.aliyuncs.com (metrics)arms-profiling-cn-hangzhou.oss-cn-hangzhou.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-hangzhou.cn-hangzhou.log.aliyuncs.com (agent self-monitoring) |
arms-dc-hz-internal.aliyuncs.com (trace and metadata)cn-hangzhou-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-hangzhou.oss-cn-hangzhou-internal.aliyuncs.com (continuous profiling)addr-hz-internal.edas.aliyun.com (ACM)end-side-logs-cn-hangzhou.cn-hangzhou-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Shanghai) |
arms-dc-sh.aliyuncs.com (trace and metadata)cn-shanghai.arms.aliyuncs.com (metrics)arms-profiling-cn-shanghai.oss-cn-shanghai.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-shanghai.cn-shanghai.log.aliyuncs.com (agent self-monitoring) |
arms-dc-sh-internal.aliyuncs.com (trace and metadata)cn-shanghai-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-shanghai.oss-cn-shanghai-internal.aliyuncs.com (continuous profiling)addr-sh-internal.edas.aliyun.com (ACM)end-side-logs-cn-shanghai.cn-shanghai-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Qingdao) |
arms-dc-qd.aliyuncs.com (trace and metadata)cn-qingdao.arms.aliyuncs.com (metrics)arms-profiling-cn-qingdao.oss-cn-qingdao.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-qingdao.cn-qingdao.log.aliyuncs.com (agent self-monitoring) |
arms-dc-qd-internal.aliyuncs.com (trace and metadata)cn-qingdao-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-qingdao.oss-cn-qingdao-internal.aliyuncs.com (continuous profiling)addr-qd-internal.edas.aliyun.com (ACM)end-side-logs-cn-qingdao.cn-qingdao-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Beijing) |
arms-dc-bj.aliyuncs.com (trace and metadata)cn-beijing.arms.aliyuncs.com (metrics)arms-profiling-cn-beijing.oss-cn-beijing.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-beijing.cn-beijing.log.aliyuncs.com (agent self-monitoring) |
arms-dc-bj-internal.aliyuncs.com (trace and metadata)cn-beijing-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-beijing.oss-cn-beijing-internal.aliyuncs.com (continuous profiling)addr-bj-internal.edas.aliyun.com (ACM)end-side-logs-cn-beijing.cn-beijing-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Zhangjiakou) |
arms-dc-zb.aliyuncs.com (trace and metadata)cn-zhangjiakou.arms.aliyuncs.com (metrics)arms-profiling-cn-zhangjiakou.oss-cn-zhangjiakou.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-zhangjiakou.cn-zhangjiakou.log.aliyuncs.com (agent self-monitoring) |
arms-dc-zb-internal.aliyuncs.com (trace and metadata)cn-zhangjiakou-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-zhangjiakou.oss-cn-zhangjiakou-internal.aliyuncs.com (continuous profiling)addr-cn-zhangjiakou-internal.edas.aliyun.com (ACM)end-side-logs-cn-zhangjiakou.cn-zhangjiakou-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Hohhot) |
dc-cn-huhehaote.arms.aliyuncs.com (trace and metadata)cn-huhehaote.arms.aliyuncs.com (metrics)arms-profiling-cn-huhehaote.oss-cn-huhehaote.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-huhehaote.cn-huhehaote.log.aliyuncs.com (agent self-monitoring) |
dc-cn-huhehaote-internal.arms.aliyuncs.com (trace and metadata)cn-huhehaote-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-huhehaote.oss-cn-huhehaote-internal.aliyuncs.com (continuous profiling)end-side-logs-cn-huhehaote.cn-huhehaote-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Ulanqab) |
dc-cn-wulanchabu.arms.aliyuncs.com (trace and metadata)cn-wulanchabu.arms.aliyuncs.com (metrics)arms-profiling-cn-wulanchabu.oss-cn-wulanchabu.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-wulanchabu.cn-wulanchabu.log.aliyuncs.com (agent self-monitoring) |
dc-cn-wulanchabu-internal.arms.aliyuncs.com (trace and metadata)cn-wulanchabu-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-wulanchabu.oss-cn-wulanchabu-internal.aliyuncs.com (continuous profiling)end-side-logs-cn-wulanchabu.cn-wulanchabu-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Shenzhen) |
arms-dc-sz.aliyuncs.com (trace and metadata)cn-shenzhen.arms.aliyuncs.com (metrics)arms-profiling-cn-shenzhen.oss-cn-shenzhen.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-shenzhen.cn-shenzhen.log.aliyuncs.com (agent self-monitoring) |
arms-dc-sz-internal.aliyuncs.com (trace and metadata)cn-shenzhen-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-shenzhen.oss-cn-shenzhen-internal.aliyuncs.com (continuous profiling)addr-sz-internal.edas.aliyun.com (ACM)end-side-logs-cn-shenzhen.cn-shenzhen-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Heyuan) |
dc-cn-heyuan.arms.aliyuncs.com (trace and metadata)cn-heyuan.arms.aliyuncs.com (metrics)arms-profiling-cn-heyuan.oss-cn-heyuan.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-heyuan.cn-heyuan.log.aliyuncs.com (agent self-monitoring) |
dc-cn-heyuan-internal.arms.aliyuncs.com (trace and metadata)cn-heyuan-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-heyuan.oss-cn-heyuan-internal.aliyuncs.com (continuous profiling)end-side-logs-cn-heyuan.cn-heyuan-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Guangzhou) |
dc-cn-guangzhou.arms.aliyuncs.com (trace and metadata)cn-guangzhou.arms.aliyuncs.com (metrics)arms-profiling-cn-guangzhou.oss-cn-guangzhou.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-guangzhou.cn-guangzhou.log.aliyuncs.com (agent self-monitoring) |
dc-cn-guangzhou-internal.arms.aliyuncs.com (trace and metadata)cn-guangzhou-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-guangzhou.oss-cn-guangzhou-internal.aliyuncs.com (continuous profiling)end-side-logs-cn-guangzhou.cn-guangzhou-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Chengdu) |
dc-cn-chengdu.arms.aliyuncs.com (trace and metadata)cn-chengdu.arms.aliyuncs.com (metrics)arms-profiling-cn-chengdu.oss-cn-chengdu.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-chengdu.cn-chengdu.log.aliyuncs.com (agent self-monitoring) |
dc-cn-chengdu-internal.arms.aliyuncs.com (trace and metadata)cn-chengdu-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-chengdu.oss-cn-chengdu-internal.aliyuncs.com (continuous profiling)end-side-logs-cn-chengdu.cn-chengdu-intranet.log.aliyuncs.com (agent self-monitoring) |
|
China (Hong Kong) |
arms-dc-hk.aliyuncs.com (trace and metadata)cn-hongkong.arms.aliyuncs.com (metrics)arms-profiling-cn-hongkong.oss-cn-hongkong.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-cn-hongkong.cn-hongkong.log.aliyuncs.com (agent self-monitoring) |
arms-dc-hk-internal.aliyuncs.com (trace and metadata)cn-hongkong-intranet.arms.aliyuncs.com (metrics)arms-profiling-cn-hongkong.oss-cn-hongkong-internal.aliyuncs.com (continuous profiling)addr-hk-internal.edas.aliyuncs.com (ACM)end-side-logs-cn-hongkong.cn-hongkong-intranet.log.aliyuncs.com (agent self-monitoring) |
|
Japan (Tokyo) |
arms-dc-jp.aliyuncs.com (trace and metadata)ap-northeast-1.arms.aliyuncs.com (metrics)arms-profiling-ap-northeast-1.oss-ap-northeast-1.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-ap-northeast-1.ap-northeast-1.log.aliyuncs.com (agent self-monitoring) |
arms-dc-jp-internal.aliyuncs.com (trace and metadata)ap-northeast-1-intranet.arms.aliyuncs.com (metrics)arms-profiling-ap-northeast-1.oss-ap-northeast-1-internal.aliyuncs.com (continuous profiling)addr-ap-northeast-1-internal.edas.aliyun.com (ACM)end-side-logs-ap-northeast-1.ap-northeast-1-intranet.log.aliyuncs.com (agent self-monitoring) |
|
Singapore |
arms-dc-sg.aliyuncs.com (trace and metadata)ap-southeast-1.arms.aliyuncs.com (metrics)arms-profiling-ap-southeast-1.oss-ap-southeast-1.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-ap-southeast-1.ap-southeast-1.log.aliyuncs.com (agent self-monitoring) |
arms-dc-sg-internal.aliyuncs.com (trace and metadata)ap-southeast-1-intranet.arms.aliyuncs.com (metrics)arms-profiling-ap-southeast-1.oss-ap-southeast-1-internal.aliyuncs.com (continuous profiling)addr-singapore-internal.edas.aliyun.com (ACM)end-side-logs-ap-southeast-1.ap-southeast-1-intranet.log.aliyuncs.com (agent self-monitoring) |
|
Malaysia (Kuala Lumpur) |
dc-ap-southeast-3.arms.aliyuncs.com (trace and metadata)ap-southeast-3.arms.aliyuncs.com (metrics)arms-profiling-ap-southeast-3.oss-ap-southeast-3.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-ap-southeast-3.ap-southeast-3.log.aliyuncs.com (agent self-monitoring) |
dc-ap-southeast-3-internal.arms.aliyuncs.com (trace and metadata)ap-southeast-3-intranet.arms.aliyuncs.com (metrics)arms-profiling-ap-southeast-3.oss-ap-southeast-3-internal.aliyuncs.com (continuous profiling)end-side-logs-ap-southeast-3.ap-southeast-3-intranet.log.aliyuncs.com (agent self-monitoring) |
|
Indonesia (Jakarta) |
arms-dc-indonesia.aliyuncs.com (trace and metadata)ap-southeast-5.arms.aliyuncs.com (metrics)arms-profiling-ap-southeast-5.oss-ap-southeast-5.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-ap-southeast-5.ap-southeast-5.log.aliyuncs.com (agent self-monitoring) |
arms-dc-indonesia-internal.aliyuncs.com (trace and metadata)ap-southeast-5-intranet.arms.aliyuncs.com (metrics)arms-profiling-ap-southeast-5.oss-ap-southeast-5-internal.aliyuncs.com (continuous profiling)end-side-logs-ap-southeast-5.ap-southeast-5-intranet.log.aliyuncs.com (agent self-monitoring) |
|
Germany (Frankfurt) |
arms-dc-frankfurt.aliyuncs.com (trace and metadata)eu-central-1.arms.aliyuncs.com (metrics)arms-profiling-eu-central-1.oss-eu-central-1.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-eu-central-1.eu-central-1.log.aliyuncs.com (agent self-monitoring) |
arms-dc-frankfurt-internal.aliyuncs.com (trace and metadata)eu-central-1-intranet.arms.aliyuncs.com (metrics)arms-profiling-eu-central-1.oss-eu-central-1-internal.aliyuncs.com (continuous profiling)addr-eu-central-1-internal.edas.aliyun.com (ACM)end-side-logs-eu-central-1.eu-central-1-intranet.log.aliyuncs.com (agent self-monitoring) |
|
UK (London) |
dc-eu-west-1.arms.aliyuncs.com (trace and metadata)eu-west-1.arms.aliyuncs.com (metrics)arms-profiling-eu-west-1.oss-eu-west-1.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-eu-west-1.eu-west-1.log.aliyuncs.com (agent self-monitoring) |
dc-eu-west-1-internal.arms.aliyuncs.com (trace and metadata)eu-west-1-intranet.arms.aliyuncs.com (metrics)arms-profiling-eu-west-1.oss-eu-west-1-internal.aliyuncs.com (continuous profiling)addr-eu-west-1-internal.edas.aliyun.com (ACM)end-side-logs-eu-west-1.eu-west-1-intranet.log.aliyuncs.com (agent self-monitoring) |
|
US (Virginia) |
dc-us-east-1.arms.aliyuncs.com (trace and metadata)us-east-1.arms.aliyuncs.com (metrics)arms-profiling-us-east-1.oss-us-east-1.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-us-east-1.us-east-1.log.aliyuncs.com (agent self-monitoring) |
dc-us-east-1-internal.arms.aliyuncs.com (trace and metadata)us-east-1-intranet.arms.aliyuncs.com (metrics)arms-profiling-us-east-1.oss-us-east-1-internal.aliyuncs.com (continuous profiling)addr-us-east-1-internal.edas.aliyun.com (ACM)end-side-logs-us-east-1.us-east-1-intranet.log.aliyuncs.com (agent self-monitoring) |
|
US (Silicon Valley) |
arms-dc-usw.aliyuncs.com (trace and metadata)us-west-1.arms.aliyuncs.com (metrics)arms-profiling-us-west-1.oss-us-west-1.aliyuncs.com (continuous profiling)acm.aliyun.com (ACM)end-side-logs-us-west-1.us-west-1.log.aliyuncs.com (agent self-monitoring) |
dc-us-west-1-internal.arms.aliyuncs.com (trace and metadata)us-west-1-intranet.arms.aliyuncs.com (metrics)arms-profiling-us-west-1.oss-us-west-1-internal.aliyuncs.com (continuous profiling)arms-dc-usw.aliyuncs.com (ACM)end-side-logs-us-west-1.us-west-1-intranet.log.aliyuncs.com (agent self-monitoring) |
Por padrão, o agente detecta automaticamente a rede e tenta usar primeiro o endpoint privado. Se não conseguir alcançá-lo, ele usará o endpoint público.
Faixas de IP a liberar
Se sua aplicação estiver implantada em uma VPC, após confirmar que os nomes de domínio privados estão acessíveis, libere the internal IP ranges for each service. Os endpoints públicos não possuem faixas de IP fixas; configure sua política de rede por nome de domínio.
Endereços IP do mecanismo ACM a liberar
O agente conecta-se ao mecanismo ACM para obter configurações. Consulte os IPs do mecanismo da sua região usando o domínio ACM:
curl 'http://acm.aliyun.com:8080/diamond-server/diamond'
Garanta que seu firewall permita o acesso aos IPs do mecanismo ACM retornados.
Requisitos de conectividade de rede para o workspace não padrão do Cloud Monitor
O workspace não padrão do Cloud Monitor usa o link de envio de dados do Simple Log Service (SLS). Por padrão, opera com protocolo HTTP, rede IPv4 e porta 80. Se a aplicação e o workspace de destino estiverem na mesma região da Alibaba Cloud, use o endpoint de service privado; caso contrário, use o endpoint de service público.
Ao usar o endpoint privado da nuvem pública do SLS, você deve configurar os endereços DNS privados da Alibaba Cloud 100.100.2.136 e 100.100.2.138. Sem essa configuração, o endereço IP virtual privado (VIP) pode não resolver corretamente.
Endpoints de service da nuvem pública
|
Região |
Endpoint de service público |
Endpoint de service privado |
|
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) (região local, em descontinuação) |
cn-nanjing.log.aliyuncs.com |
cn-nanjing-intranet.log.aliyuncs.com |
|
China (Fuzhou) (região local, em descontinuação) |
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 |
|
Japan (Tokyo) |
ap-northeast-1.log.aliyuncs.com |
ap-northeast-1-intranet.log.aliyuncs.com |
|
South Korea (Seoul) |
ap-northeast-2.log.aliyuncs.com |
ap-northeast-2-intranet.log.aliyuncs.com |
|
Singapore |
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 |
|
Philippines (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 |
|
UAE (Dubai) |
me-east-1.log.aliyuncs.com |
me-east-1-intranet.log.aliyuncs.com |
|
Germany (Frankfurt) |
eu-central-1.log.aliyuncs.com |
eu-central-1-intranet.log.aliyuncs.com |
|
UK (London) |
eu-west-1.log.aliyuncs.com |
eu-west-1-intranet.log.aliyuncs.com |
|
US (Virginia) |
us-east-1.log.aliyuncs.com |
us-east-1-intranet.log.aliyuncs.com |
|
US (Silicon Valley) |
us-west-1.log.aliyuncs.com |
us-west-1-intranet.log.aliyuncs.com |
Para mais informações sobre endpoints de service, consulte Service endpoints for different network types in Simple Log Service.
Verificar automaticamente a conectividade de rede
Pré-requisitos
Instale curl e nc no container ou máquina onde a aplicação executa. O script usa curl -4 para forçar requisições HTTP via IPv4, com timeout de conexão de 1 segundo para todas as verificações.
Executar o script de verificação automatizada
-
Crie o arquivo
check_network.she adicione o seguinte conteúdo:#!/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" -
Conceda permissão de execução e execute o script:
chmod +x check_network.sh ./check_network.sh ${region_id}O parâmetro
${region_id}é o ID da região onde o workspace está localizado, por exemplo,cn-hangzhou. Se esse parâmetro não for fornecido, o script tentará obter o ID da região dos metadados da instância ECS atual.
O script verifica o link original de envio do ARMS para o workspace padrão do Cloud Monitor e os endpoints de service público e privado do SLS para o workspace não padrão. Pelo menos um link (público ou privado) compatível com a rede da sua implantação deve estar acessível.