View endpoints and data reporting protocols by region and port -

Managed Service for OpenTelemetry ingests data from open source clients, including OpenTelemetry SDKs and Collectors, Jaeger SDKs and Agents, Zipkin, and Skywalking. This topic describes the service endpoints for each region, the protocols supported on each port, and how to get an authentication token.

Direct data reporting

Endpoints by region

Note

If your application is deployed on Alibaba Cloud, use the Alibaba Cloud private endpoint. Otherwise, use the public endpoint.

Region	Region ID	Alibaba Cloud private endpoint	Public endpoint
China (Hangzhou)	cn-hangzhou	tracing-analysis-dc-hz-internal.aliyuncs.com	tracing-analysis-dc-hz.aliyuncs.com
China (Shanghai)	cn-shanghai	tracing-analysis-dc-sh-internal.aliyuncs.com	tracing-analysis-dc-sh.aliyuncs.com
China (Qingdao)	cn-qingdao	tracing-analysis-dc-qd-internal.aliyuncs.com	tracing-analysis-dc-qd.aliyuncs.com
China (Beijing)	cn-beijing	tracing-analysis-dc-bj-internal.aliyuncs.com	tracing-analysis-dc-bj.aliyuncs.com
China (Zhangjiakou)	cn-zhangjiakou	tracing-analysis-dc-zb-internal.aliyuncs.com	tracing-analysis-dc-zb.aliyuncs.com
China (Hohhot)	cn-huhehaote	tracing-cn-huhehaote-internal.arms.aliyuncs.com	tracing-cn-huhehaote.arms.aliyuncs.com
China (Ulanqab)	cn-wulanchabu	tracing-cn-wulanchabu-internal.arms.aliyuncs.com	tracing-cn-wulanchabu.arms.aliyuncs.com
China (Shenzhen)	cn-shenzhen	tracing-analysis-dc-sz-internal.aliyuncs.com	tracing-analysis-dc-sz.aliyuncs.com
China (Heyuan)	cn-heyuan	tracing-cn-heyuan-internal.arms.aliyuncs.com	tracing-cn-heyuan.arms.aliyuncs.com
China (Guangzhou)	cn-guangzhou	tracing-cn-guangzhou-internal.arms.aliyuncs.com	tracing-cn-guangzhou.arms.aliyuncs.com
China (Chengdu)	cn-chengdu	tracing-cn-chengdu-internal.arms.aliyuncs.com	tracing-cn-chengdu.arms.aliyuncs.com
China (Hong Kong)	cn-hongkong	tracing-analysis-dc-hk-internal.aliyuncs.com	tracing-analysis-dc-hk.aliyuncs.com
Japan (Tokyo)	ap-northeast-1	tracing-analysis-dc-jp-internal.aliyuncs.com	tracing-analysis-dc-jp.aliyuncs.com
Singapore	ap-southeast-1	tracing-analysis-dc-sg-internal.aliyuncs.com	tracing-analysis-dc-sg.aliyuncs.com
Malaysia (Kuala Lumpur)	ap-southeast-3	tracing-ap-southeast-3-internal.arms.aliyuncs.com	tracing-ap-southeast-3.arms.aliyuncs.com
Indonesia (Jakarta)	ap-southeast-5	tracing-analysis-dc-indonesia-internal.aliyuncs.com	tracing-analysis-dc-indonesia.aliyuncs.com
Germany (Frankfurt)	eu-central-1	tracing-analysis-dc-frankfurt-internal.aliyuncs.com	tracing-analysis-dc-frankfurt.aliyuncs.com
UK (London)	eu-west-1	tracing-analysis-dc-lundun-internal.aliyuncs.com	tracing-analysis-dc-lundun.aliyuncs.com
US (Silicon Valley)	us-west-1	tracing-analysis-dc-usw-internal.aliyuncs.com	tracing-analysis-dc-usw.aliyuncs.com
US (Virginia)	us-east-1	tracing-us-east-1-internal.arms.aliyuncs.com	tracing-us-east-1.arms.aliyuncs.com

Supported protocols by port

Port number	Protocol	Description
80	OpenTelemetry HTTP Jaeger HTTP Jaeger Remote Sampling Zipkin HTTP	The URL path determines the protocol. OpenTelemetry HTTP: /api/otlp/traces Jaeger HTTP: /api/traces Jaeger Remote Sampling: /api/sampling Zipkin HTTP: v1: /api/v1/spans v2: /api/v2/spans
443	OpenTelemetry HTTPS Jaeger HTTPS Jaeger Remote Sampling Zipkin HTTPS	The URL path determines the protocol. OpenTelemetry HTTPS: /api/otlp/traces Jaeger HTTPS: /api/traces Jaeger Remote Sampling: /api/sampling Zipkin HTTPS: v1: /api/v1/spans v2: /api/v2/spans
1883	Jaeger gRPC Skywalking gRPC	None
8000	Skywalking v8 gRPC	None
8090	OpenTelemetry gRPC	None

Obtain an authentication token

After you activate Managed Service for OpenTelemetry, you must get a token from the console to authenticate your data.

New console

Log on to the Managed Service for OpenTelemetry console. In the left-side navigation pane, click Integration Center.
In the Open Source Frameworks section, click the card for your client, for example, OpenTelemetry.
In the panel that appears, go to the Start Integration tab. Select a region, set the Connection Method to Alibaba Cloud Private Network or Public Network, and set the Reporting Method to HTTP or gRPC. In the Access Point Information section, find the endpoint URL, which contains your token.
Note
- For OpenTelemetry HTTP, Zipkin HTTP, and Jaeger HTTP, the token is part of the HTTP URL.
- For Skywalking gRPC, OpenTelemetry gRPC, and Jaeger gRPC, provide the token as Authentication=<token> in the gRPC metadata for server-side authentication.

Old console

Log on to the Managed Service for OpenTelemetry console.
In the left-side navigation pane, click Cluster Configurations, and then click the Access Point Information tab.
At the top of the page, select the region to which you want to connect. In the Cluster Information section, enable the Show Token switch.
In the Client section, click the client that you want to use, for example, OpenTelemetry.

The Related Information column shows the access point information for the selected region. For reporting data over HTTP, the URLs for the public endpoint and Alibaba Cloud VPC endpoint include the path /adapt_xxx/api/otlp/traces and your token. For reporting data over gRPC, this section lists the public endpoint (port 8090), VPC endpoint (port 8090), and the authentication token. If you use Go to report data, remove the http:// prefix from the endpoint.
Note
- For OpenTelemetry HTTP, Zipkin HTTP, and Jaeger HTTP, the token is part of the HTTP URL.
- For Skywalking gRPC, OpenTelemetry gRPC, and Jaeger gRPC, provide the token as Authentication=<token> in the gRPC metadata for server-side authentication.