{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/245", "result": {"data":{"issuesJson":{"id":"7e32d44c-0bea-58b9-a483-9c48e055a8ff","title":"jaegertracing/jaeger: 开源、分布式跟踪平台","number":245,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Reposjaegertracing/jaeger
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n

\"Stand

\n

\n

\"Slack
\n\"Unit
\n\"Coverage
\n\"Project+Community
\n\"FOSSA
\n\"OpenSSF
\n\"OpenSSF
\n\"CLOMonitor\"
\n\"Artifact

\n

\n

Jaeger - a Distributed Tracing System

\n

💥💥💥 Jaeger v2 is out! Read the blog post and try it out.

\n
\n
\n
\n 
graph TD\n    SDK[\"OpenTelemetry SDK\"] --> |HTTP or gRPC| COLLECTOR\n    COLLECTOR[\"Jaeger Collector\"] --> STORE[Storage]\n    COLLECTOR --> |gRPC| PLUGIN[Storage Plugin]\n    COLLECTOR --> |gRPC/sampling| SDK\n    PLUGIN --> STORE\n    QUERY[Jaeger Query Service] --> STORE\n    QUERY --> |gRPC| PLUGIN\n    UI[Jaeger UI] --> |HTTP| QUERY\n    subgraph Application Host\n        subgraph User Application\n            SDK\n        end\n    end\n
\n
\n
\n \n \n Loading\n\n \n
\n\n

Jaeger is a distributed tracing platform created by Uber Technologies and donated to Cloud Native Computing Foundation.

\n

See Jaeger documentation for getting started, operational details, and other information.

\n

Jaeger is hosted by the Cloud Native Computing Foundation (CNCF) as the 7th top-level project, graduated in October 2019. See the CNCF Jaeger incubation announcement and Jaeger graduation announcement.

\n

Get Involved

\n

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 for how to get involved. Many of them do not even require any coding.

\n

Version Compatibility Guarantees

\n

Since Jaeger uses many components from the OpenTelemetry Collector we try to maintain configuration compatibility between Jaeger releases. Occasionally, configuration options in Jaeger (or in Jaeger v1 CLI flags) can be deprecated due to usability improvements, new functionality, or changes in our dependencies.
\nIn such situations, developers introducing the deprecation are required to follow these guidelines.

\n

In short, for a deprecated configuration option, you should expect to see the following message in the documentation or release notes:

\n
(deprecated, will be removed after yyyy-mm-dd or in release vX.Y.Z, whichever is later)\n
\n

A grace period of at least 3 months or two minor version bumps (whichever is later) from the first release
\ncontaining the deprecation notice will be provided before the deprecated configuration option can be deleted.

\n

For example, consider a scenario where v2.0.0 is released on 01-Sep-2024 containing a deprecation notice for a configuration option.
\nThis configuration option will remain in a deprecated state until the later of 01-Dec-2024 or v2.2.0 where it can be removed on or after either of those events.
\nIt may remain deprecated for longer than the aforementioned grace period.

\n

Go Version Compatibility Guarantees

\n

The Jaeger project attempts to track the currently supported versions of Go, as defined by the Go team.
\nRemoving support for an unsupported Go version is not considered a breaking change.

\n

Starting with the release of Go 1.21, support for Go versions will be updated as follows:

\n
    \n
  1. Soon after the release of a new Go minor version N, updates will be made to the build and tests steps to accommodate the latest Go minor version.
    2. \n
  2. Soon after the release of a new Go minor version N, support for Go version N-2 will be removed and version N-1 will become the minimum required version.
    3. \n
\n

Related Repositories

\n

Components

\n\n

Documentation

\n\n

Building From Source

\n

See CONTRIBUTING.

\n

Contributing

\n

See CONTRIBUTING.

\n

Thanks to all the people who already contributed!

\n\n \n\n

Maintainers

\n

Rules for becoming a maintainer are defined in the GOVERNANCE document.
\nThe official maintainers of the Jaeger project are listed in the MAINTAINERS file.
\nPlease use @jaegertracing/jaeger-maintainers to tag them on issues / PRs.

\n

Some repositories under jaegertracing org have additional maintainers.

\n

Project Status Meetings

\n

The Jaeger maintainers and contributors meet regularly on a video call. Everyone is welcome to join, including end users. For meeting details, see https://www.jaegertracing.io/get-in-touch/.

\n

Roadmap

\n

See https://www.jaegertracing.io/docs/roadmap/

\n

Get in Touch

\n

Have questions, suggestions, bug reports? Reach the project community via these channels:

\n\n

Security

\n

Third-party security audits of Jaeger are available in https://github.com/jaegertracing/security-audits. Please see Issue #1718 for the summary of available security mechanisms in Jaeger.

\n

Adopters

\n

Jaeger as a product consists of multiple components. We want to support different types of users,
\nwhether they are only using our instrumentation libraries or full end to end Jaeger installation,
\nwhether it runs in production or you use it to troubleshoot issues in development.

\n

Please see ADOPTERS.md for some of the organizations using Jaeger today.
\nIf you would like to add your organization to the list, please comment on our
\nsurvey issue.

\n

Sponsors

\n

The Jaeger project owes its success in open source largely to the Cloud Native Computing Foundation (CNCF), our primary supporter. We deeply appreciate their vital support. Furthermore, we are grateful to Uber for their initial, project-launching donation, and for the continuous contributions of software and infrastructure from 1Password, Codecov.io, Dosu, GitHub, Google Analytics, Netlify, and Oracle Cloud Infrastructure. Thank you for your generous support.

\n

License

\n

Copyright (c) The Jaeger Authors. Apache 2.0 License.

","updatedAt":"2025-05-21T16:03:03Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"Monitor","color":"533a1e"}},{"node":{"name":"jaegertracing","color":"92a378"}}]},"comments":{"edges":[]}}},"pageContext":{"number":245,"previous":{"title":"istio/istio: Istio 是一个开源服务网格，它透明地分层到现有的分布式应用程序上。","number":244},"next":{"title":"kairyou/jenkins-cli: 一个用 Rust 编写的强大高效的 Jenkins CLI 工具。通过命令行简化 Jenkins 的项目部署。","number":246}}}, "staticQueryHashes": ["151096407","2861350382"]}