Skip to content
CNCF Jaeger, a Distributed Tracing System
Branch: master
Clone or download
annanay25 and yurishkuro Adds support for agent level tag (#1396)
* Basic POC for agent based tags

Signed-off-by: Annanay <annanay.a@media.net>

* Address comments

Signed-off-by: Annanay <annanay.a@media.net>

* Rebased

Signed-off-by: Annanay <annanay.a@media.net>

* Fix tests and build errors

Signed-off-by: Annanay <annanay.a@media.net>

* Address comments

Signed-off-by: Annanay <annanay.a@media.net>

* nit, fix tests

Signed-off-by: Annanay <annanay.a@media.net>

nit, fix function call

Signed-off-by: Annanay <annanay.a@media.net>

nit, fix function call

Signed-off-by: Annanay <annanay.a@media.net>

fix fmt, gosimple

Signed-off-by: Annanay <annanay.a@media.net>

make fmt

* Start adding tests

Signed-off-by: Annanay <annanay.a@media.net>

Fix tag names

Signed-off-by: Annanay <annanay.a@media.net>

* Fix TestCollectorProxy test

Signed-off-by: Annanay <annanay.a@media.net>

* Tags are added in send, not in EmitZipkinBatch

Signed-off-by: Annanay <annanay.a@media.net>

* Addressed comments, added tests

Signed-off-by: Annanay <annanay.a@media.net>

* Remove debug print

Signed-off-by: Annanay <annanay.a@media.net>

* Remove all changes to tchannel reporter

Signed-off-by: Annanay <annanay.a@media.net>

* Add tests, fix code coverage

Signed-off-by: Annanay <annanay.a@media.net>

* Address comments, run make fmt

Signed-off-by: Annanay <annanay.a@media.net>

* Addressed comments

Signed-off-by: Annanay <annanay.a@media.net>

* Address comments

Signed-off-by: Annanay <annanay.a@media.net>

* Address comments

Signed-off-by: Annanay <annanay.a@media.net>
Latest commit 8e76a50 Mar 18, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
cmd Adds support for agent level tag (#1396) Mar 18, 2019
crossdock Increase grpc retry to 1000 in xdock (#1419) Mar 11, 2019
docker-compose Make grpc reporter default and add retry (#1384) Feb 27, 2019
examples/hotrod Rewrite if-else to switch statements (#1412) Mar 12, 2019
idl @ 347af16
internal/tracegen Add tracegen utility for generating traces (#1245) Jan 17, 2019
jaeger-ui @ 75a7069
model Rewrite if-else to switch statements (#1412) Mar 12, 2019
pkg Fix spelling in logger_test.go (#1390) Feb 28, 2019
plugin
proto-gen Add gRPC communication between agent and collector (#1165) Nov 13, 2018
scripts Alphabetically sort imports in python scripts (#1381) Feb 26, 2019
storage Add a Downsampling writer that drop a percentage of spans (#1353) Mar 12, 2019
swagger-gen Collect Zipkin v2 json (#518) Nov 16, 2017
thrift-gen Fix import grouping (#1080) Sep 24, 2018
.codecov.yml Require 100% coverage (#909) Jul 3, 2018
.gitignore
.gitmodules
.travis.yml Skip deploy in non deploy jobs (#1358) Feb 18, 2019
ADOPTERS.md Change http to https for security links (#1345) Feb 14, 2019
CHANGELOG.md Remove deprecated kafka flags (#1424) Mar 17, 2019
CODEOWNERS
CODE_OF_CONDUCT.md Add CNCF Code of Conduct (#415) Sep 22, 2017
CONTRIBUTING.md Dep migration (#1240) Dec 7, 2018
CONTRIBUTING_GUIDELINES.md
DCO Add DCO and updade CONTRIBUTING.md accordingly Sep 17, 2017
GOVERNANCE.md Change maintainer nominations to public (#534) Nov 14, 2017
Gopkg.lock
Gopkg.toml
LICENSE
Makefile
README.md
RELEASE.md Add documentation step into release guide (#1295) Jan 22, 2019
doc.go Finish replacing uber/jaeger with jaegertracing/jaeger (#537) Nov 14, 2017

README.md

Build Status Coverage Status Gitter chat OpenTracing-1.0 FOSSA Status CII Best Practices Project+Community stats

Jaeger - a Distributed Tracing System

Jaeger, inspired by Dapper and OpenZipkin, is a distributed tracing system released as open source by Uber Technologies. 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 is hosted by the Cloud Native Computing Foundation (CNCF). 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 announcement.

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 ground up to support the OpenTracing standard.

  • Represent traces as directed acyclic graphs (not just trees) via span references
  • Support strongly typed span tags and structured logs
  • Support general distributed context propagation mechanism via baggage

Multiple storage backends

Jaeger supports two popular open source NoSQL databases as trace storage backends: Cassandra 3.4+ and Elasticsearch 5.x/6.x. 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 and a Helm chart.

Observability

All Jaeger backend components expose Prometheus metrics by default (other metrics backends are also supported). Logs are written to standard out using the structured logging library zap.

Backwards compatibility with Zipkin

Although we recommend instrumenting applications with OpenTracing API and binding to Jaeger client libraries to benefit from advanced features not available elsewhere, 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.

Related Repositories

Documentation

Instrumentation Libraries

Deployment

Components

Building From Source

See CONTRIBUTING.

Contributing

See CONTRIBUTING.

Maintainers

Below are the official maintainers of the Jaeger project. Please use @jaegertracing/jaeger-maintainers to tag them on issues / PRs.

Some repositories under jaegertracing org have additional maintainers.

Project Status Bi-Weekly Meeting

The Jaeger contributors meet bi-weekly, and everyone is welcome to join. Agenda and meeting details here.

Roadmap

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

Questions, Discussions, Bug Reports

Reach project contributors via these channels:

Adopters

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

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

License

Apache 2.0 License.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.