golang分布式链路追踪系统-jaeger

<img align="right" width="290" height="290" src="https://www.jaegertracing.io/img/jaeger-vector.svg"> [![Slack chat][slack-img]](#get-in-touch) [![Project+Community stats][community-badge]][community-stats] [![Unit Tests][ci-img]][ci] [![Coverage Status][cov-img]][cov] [![FOSSA Status][fossa-img]](https://app.fossa.io/projects/git%2Bgithub.com%2Fjaegertracing%2Fjaeger?ref=badge_shield) [![Artifact Hub][artifacthub-img]](https://artifacthub.io/packages/helm/jaegertracing/jaeger) [](https://bestpractices.coreinfrastructure.org/projects/1273) <img src="https://github.com/cncf/artwork/blob/master/other/cncf-member/graduated/color/cncf-graduated-color.svg" width="250"> # Jaeger - a Distributed Tracing System ```mermaid graph TD LIB --> |HTTP or gRPC| COLLECTOR LIB[Jaeger Client] --> |UDP| AGENT[Jaeger Agent] %% AGENT --> |HTTP/sampling| LIB AGENT --> |gRPC| COLLECTOR[Jaeger Collector] %% COLLECTOR --> |gRPC/sampling| AGENT SDK[OpenTelemetry SDK] --> |UDP| AGENT SDK --> |HTTP or gRPC| COLLECTOR COLLECTOR --> STORE[Storage] COLLECTOR --> |gRPC| PLUGIN[Storage Plugin] PLUGIN --> STORE QUERY[Jaeger Query Service] --> STORE QUERY --> |gRPC| PLUGIN UI[Jaeger UI] --> |HTTP| QUERY subgraph Application Host subgraph User Application LIB SDK end AGENT end ``` Jaeger, inspired by [Dapper][dapper] and [OpenZipkin](https://zipkin.io), is a distributed tracing platform created by [Uber Technologies][ubeross] and donated to [Cloud Native Computing Foundation](https://cncf.io). It can be used for monitoring microservices-based distributed systems: * Distributed context propagation * Distributed transaction monitoring * Root cause analysis * Service dependency analysis * Performance / latency optimization See also: * Jaeger [documentation][doc] for getting started, operational details, and other information. * Blog post [Evolving Distributed Tracing at Uber](https://eng.uber.com/distributed-tracing/). * Tutorial / walkthrough [Take Jaeger for a HotROD ride][hotrod-tutorial]. Jaeger is hosted by the [Cloud Native Computing Foundation](https://cncf.io) (CNCF) as the 7th top-level project (graduated in October 2019). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Jaeger plays a role, read the CNCF [Jaeger incubation announcement](https://www.cncf.io/blog/2017/09/13/cncf-hosts-jaeger/) and [Jaeger graduation announcement](https://www.cncf.io/announcement/2019/10/31/cloud-native-computing-foundation-announces-jaeger-graduation/). ## Get Involved Jaeger is an open source project with open governance. We welcome contributions from the community, and we would love your help to improve and extend the project. Here are [some ideas](https://www.jaegertracing.io/get-involved/) for how to get involved. Many of them do not even require any coding. ## Features ### High Scalability Jaeger backend is designed to have no single points of failure and to scale with the business needs. For example, any given Jaeger installation at Uber is typically processing several billions of spans per day. ### Native support for OpenTracing Jaeger backend, Web UI, and instrumentation libraries have been designed from the ground up to support the [OpenTracing standard](https://opentracing.io/specification/). * Represent traces as directed acyclic graphs (not just trees) via [span references](https://github.com/opentracing/specification/blob/master/specification.md#references-between-spans) * Support strongly typed span _tags_ and _structured logs_ * Support general distributed context propagation mechanism via _baggage_ #### OpenTelemetry Jaeger project recommends OpenTelemetry SDKs for instrumentation, instead of Jaeger's native SDKs [that are now deprecated](https://www.jaegertracing.io/docs/latest/client-libraries/#deprecating-jaeger-clients). The OpenTracing and OpenCensus projects have merged into a new CNCF project called [OpenTelemetry](https://opentelemetry.io). The Jaeger and OpenTelemetry projects have different goals. OpenTelemetry aims to provide APIs and SDKs in multiple languages to allow applications to export various telemetry data out of the process, to any number of metrics and tracing backends. The Jaeger project is primarily the tracing backend that receives tracing telemetry data and provides processing, aggregation, data mining, and visualizations of that data. The Jaeger client libraries do overlap with OpenTelemetry in functionality. OpenTelemetry natively supports Jaeger as a tracing backend and makes Jaeger native clients unnecessary. For more information please refer to a blog post [Jaeger and OpenTelemetry](https://medium.com/jaegertracing/jaeger-and-opentelemetry-1846f701d9f2). ### Multiple storage backends Jaeger supports two popular open source NoSQL databases as trace storage backends: Cassandra and Elasticsearch. There is also embedded database support using [Badger](https://github.com/dgraph-io/badger). There are ongoing community experiments using other databases, such as ScyllaDB, InfluxDB, Amazon DynamoDB. Jaeger also ships with a simple in-memory storage for testing setups. ### Modern Web UI Jaeger Web UI is implemented in Javascript using popular open source frameworks like React. Several performance improvements have been released in v1.0 to allow the UI to efficiently deal with large volumes of data and to display traces with tens of thousands of spans (e.g. we tried a trace with 80,000 spans). ### Cloud Native Deployment Jaeger backend is distributed as a collection of Docker images. The binaries support various configuration methods, including command line options, environment variables, and configuration files in multiple formats (yaml, toml, etc.) Deployment to Kubernetes clusters is assisted by [Kubernetes templates](https://github.com/jaegertracing/jaeger-kubernetes) and a [Helm chart](https://github.com/jaegertracing/helm-charts). ### Observability All Jaeger backend components expose [Prometheus](https://prometheus.io/) metrics by default (other metrics backends are also supported). Logs are written to standard out using the structured logging library [zap](https://github.com/uber-go/zap). ### Security Third-party security audits of Jaeger are available in https://github.com/jaegertracing/security-audits. Please see [Issue #1718](https://github.com/jaegertracing/jaeger/issues/1718) for the summary of available security mechanisms in Jaeger. ### Backwards compatibility with Zipkin Although we recommend instrumenting applications with OpenTelemetry, if your organization has already invested in the instrumentation using Zipkin libraries, you do not have to rewrite all that code. Jaeger provides backwards compatibility with Zipkin by accepting spans in Zipkin formats (Thrift or JSON v1/v2) over HTTP. Switching from Zipkin backend is just a matter of routing the traffic from Zipkin libraries to the Jaeger backend. ## Version Compatibility Guarantees Occasionally, CLI flags can be deprecated due to, for example, usability improvements or new functionality. In such situations, developers introducing the deprecation are required to follow [these guidelines](./CONTRIBUTING.md#deprecating-cli-flags). In short, for a deprecated CLI flag, you should expect to see the following message in the `--help` documentation: ``` (deprecated, will be removed after yyyy-mm-dd or in release vX.Y.Z, whichever is later) ``` A grace period of at least **3 months** or **two minor version bumps** (whichever is later) from the first release containing the deprecation notice will be provided before the deprecated CLI flag _can_ be deleted. For example, consider a scen