Fully grasp the theory and practice of Jaeger's distributed call link tracking, Go integrates link tracking jaeger for all HTTP requests using the go-resty library (with source code).
Introduce Jaeger, an open source distributed tracking system. First, learn from the theoretical basics. You will learn how to integrate link tracking in HTTP requests, and how to implement it in the GORM framework. Finally, you will learn the source code of the go-zero framework integrated link tracking.
In my daily development, our project is based on the microservice architecture implemented by go-zero, and the calling relationship between various services/modules is very complicated. The go-zero framework has implemented link tracking from api-rpc and rpc-rpc services, saving us a lot of work. However, when we call third-party libraries, it is inevitable that there is no integrated link tracking and we need to add it ourselves, such as accessing others through http requests.
Since Jaeger is developed using Golang, most people who use the Go technology stack will use it as the first choice.
Overview
Contemporary Internet services are usually implemented using complex, large-scale distributed clusters. Internet applications are built on different sets of software modules. These software modules may be developed by different teams, may be implemented using different programming languages, and may be deployed on thousands of servers, spanning multiple different data center. Therefore, there is a need for tools that can help understand system behavior and analyze performance issues.
Inspired by Dapper and OpenZipkin, Jaeger is a distributed tracing system released as open source by Uber Technologies. It is used for monitoring and troubleshooting microservices-based distributed systems, including:
Distributed Context Propagation
Distributed Transaction Monitoring
Root Cause Analysis
Service Dependency Analysis
Performance/Latency Optimization
example
For example, a front-end service may initiate a web query to hundreds of query servers, and each query has its own Ind