You can connect the following types of clients to Tracing Analysis: the ARMS OpenTelemetry Collector, the open source OpenTelemetry Collector, the Jaeger agent, the Zipkin collector, and the SkyWalking client. You can also connect to Tracing Analysis by using open source OpenTelemetry SDKs and Jaeger SDKs. This topic describes the regions and endpoints that are supported by Tracing Analysis and the data reporting protocols that are supported by different ports.
Directly report data
Alibaba Cloud regions and endpoints that are supported by Tracing Analysis
Note If your application is deployed in an Alibaba Cloud production environment, select a private endpoint. Otherwise, select a public endpoint.
| Region | Region ID | 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 |
| Australia (Sydney) | ap-southeast-2 | tracing-ap-southeast-2-internal.arms.aliyuncs.com | tracing-ap-southeast-2.arms.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 |
| India (Mumbai) | ap-south-1 | tracing-ap-south-1-internal.arms.aliyuncs.com | tracing-ap-south-1.arms.aliyuncs.com |
Protocols that are supported by different ports
| Port number | Protocol | Description |
|---|---|---|
| 80 |
| Different protocols are distinguished by URL suffixes.
|
| 443 |
| Different protocols are distinguished by URL suffixes.
|
| 1883 |
| None |
| 8000 | Skywalking v8 gRPC | None |
| 8090 | OpenTelemetry gRPC | None |
Obtain an authentication token
After you activate Tracing Analysis, you can obtain a token to authenticate the reported data. To obtain the token, perform the following steps:
- Log on to the Tracing Analysis console.
- In the left-side navigation pane, click Cluster Configurations. Then, click the Access point information tab.
- In the top navigation bar, select a region. In the Cluster Information section, turn on Show Token.
- In the Client section, select the client that you want to use to collect trace data. In this example, Jaeger is selected.
- In the Related Information column of the table, click the copy icon next to the endpoint that you want to use.
- If you use OpenTelemetry HTTP, Zipkin HTTP, or Jaeger HTTP, the token is contained in an HTTP URL.
- If you use SkyWalking gRPC, OpenTelemetry gRPC, or Jaeger gRPC, the system specifies
Authentication=<token>in themetadataof gRPC and then sends the metadata to the server for authentication.