How to install the Jaeger agent-Managed Service for OpenTelemetry(OpenTelemetry)-阿里云帮助中心

Managed Service for OpenTelemetry allows you to use OpenTelemetry, Jaeger, Zipkin, and SkyWalking clients to report application trace data to the console. This topic describes how to install the Jaeger agent.

Step 1: Obtain an endpoint

New console

Log on to the Managed Service for OpenTelemetry console. In the left-side navigation pane, click Integration Center.
In the Server-side Applications area, click the Jaeger card.
In the Jaeger panel, select the region where you want to report data.

Note
Resources are automatically provisioned the first time you access a region.
Select a Connection Type and an Export Protocol, and then copy the endpoint information.
- Connection Type: If your service is deployed on Alibaba Cloud and its region is the same as the selected integration region, use the Alibaba Cloud VPC network. Otherwise, use the public network.
- Export Protocol: Select the protocol that your client supports. For example, you can select gRPC.
The command for the gRPC agent method is in the format ./jaeger-agent --reporter.grpc.host-port=<Endpoint Address>:1883 --agent.tags=Authentication=<Token>. The endpoint address is automatically generated based on the selected region and connection type. Use the --agent.tags parameter for Jaeger Agent 1.15 or later. For earlier versions, use --jaeger.tags.

Old console

Log on to the Managed Service for OpenTelemetry console.
In the left-side navigation pane, click Cluster Configurations, and then click the Endpoint Information tab on the right.
At the top of the page, select the region to integrate, and then turn on the Show Token switch in the Cluster Information area.
In the Client-side Collection Tools area, click Jaeger.

In the Related Information column, obtain the endpoint information. After you click Jaeger, the page displays a table with endpoints for the current region, such as China (Shanghai). The data reporting method is Direct reporting. The Related Information column contains URLs for reporting data over HTTP (for public and Alibaba Cloud VPC networks) and commands for reporting data via an agent (for public and VPC networks). For example, the agent command for the public network is ./jaeger-agent --reporter.grpc.host-port=tracing-analysis-dc-sh.aliyuncs.com:1883 --agent.tags=Authentication=<Token>. Copy the required endpoint for your client configuration. Note: The command shown uses --agent.tags, which is compatible with Jaeger Agent 1.15 and later. For earlier versions, use --jaeger.tags.

Note
If your application is deployed on Alibaba Cloud in the same region as the selected integration region, use the Alibaba Cloud VPC network endpoint. Otherwise, use the public network endpoint.

Step 2: Download and start the Jaeger agent

ECS clusters

If your application is deployed in an Elastic Compute Service (ECS) cluster, you can start the Jaeger agent by performing the following operations:

Download and decompress the installation package of the Jaeger agent.
Note
We recommend that you download the latest version of the Jaeger agent.
Run the following command to start the Jaeger agent:
```
nohup ./jaeger-agent --reporter.grpc.host-port=<endpoint> --agent.tags=<token>
```
Note
- If your Jaeger agent is of V1.15.0 or an earlier version, replace --agent.tags with --jaeger.tags.
- Replace <endpoint> with the endpoint that you obtained in Step 1.
- Replace <token> with the token that you obtained in Step 1.

Docker containers

If your application is deployed in a Docker container, we recommend that you start the Jaeger agent by running the docker run command. This reduces your O&M costs. Run the following command to start the Jaeger agent:

docker run -d\
  --rm \
  -p5775:5775/udp \
  -p6831:6831/udp \
  -p6832:6832/udp \
  -p5778:5778/tcp \
  jaegertracing/jaeger-agent:<version> \
  --reporter.grpc.host-port=<endpoint> \
  --agent.tags=<token>

Note

Perform the following operations on the parameters in the docker run command:

If your Jaeger agent is of V1.15.0 or an earlier version, replace --agent.tags with --jaeger.tags.
Replace <version> with the version of the Jaeger agent, such as 1.23. For more information about other available versions, visit jaegertracing/jaeger-agent.
Replace <endpoint> with the endpoint that you obtained in Step 1.
Replace <token> with the token that you obtained in Step 1.

上一篇: Record and analyze exceptions with open source tracing clients 下一篇: Embed Managed Service for OpenTelemetry console pages in a self-managed web application