# Jaeger

CNCF Jaeger, a Distributed Tracing Platform

Repository: https://github.com/jaegertracing/jaeger
Canonical: https://ross.abutalabs.com/products/jaeger
Homepage: https://www.jaegertracing.io/
Language: Go
License: Apache-2.0
License Family: permissive
Topics: distributed-tracing, cncf, tracing, observability, jaeger, opentelemetry, hacktoberfest
Last push: 2026-08-26T19:05:57+00:00
Link (homepage): https://www.jaegertracing.io/
Link (site_page): https://www.jaegertracing.io/docs/latest
Link (site_page): https://www.jaegertracing.io/docs/2.20/getting-started

## Health v2 (maintenance only)
Score: 97/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 93, longevity 100
- inputs: {"age_days": 3792, "days_push": 7, "days_rel": 44, "gap_med": 28.5, "n_releases_24m": 25}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 23145, forks 3098 (observed 2026-08-28T04:11:34.536359+00:00)

## What it is
Jaeger is a CNCF-graduated, open-source distributed tracing platform originally created at Uber, used to monitor and troubleshoot request flows across microservices. Version 2 is built on the OpenTelemetry Collector framework and includes a collector, query service, storage backends (e.g., ClickHouse, Elasticsearch, Cassandra), and a web UI for visualizing traces.

## Use cases
- trace requests across microservices to find latency bottlenecks
- troubleshoot errors in distributed systems with end-to-end request timelines
- visualize service dependency graphs
- collect and store OpenTelemetry traces via OTLP
- self-host a tracing backend for Kubernetes clusters
- analyze root causes of performance problems in production

## When to choose
- you run microservices and need distributed tracing with a mature UI
- you already use OpenTelemetry SDKs and need a trace collector and query backend
- you want a CNCF-graduated, vendor-neutral observability component
- you need pluggable storage backends like ClickHouse, Elasticsearch, or Cassandra

## When to avoid
- you only need metrics or logs without trace correlation
- you want a fully managed SaaS tracing product with zero infrastructure
- your stack is single-process and tracing adds little value
- you need profiling or continuous profiling features rather than request tracing

## Facets
- artifact type: service
- maturity: stable
- function: tracing, monitoring, http-server, web-framework
- domain: monitoring, microservices
- platform: self-hosted, cloud, go, windows
- tags: distributed-tracing, opentelemetry, cncf, observability, microservices, trace-analysis, service-dependency-graph, devops, docker, kubernetes, linux, macos

## Member repositories
- jaegertracing/jaeger (main) score 97
- jaegertracing/jaeger-ui (frontend) score 97
- jaegertracing/jaeger-client-go (sdk) score 10
- jaegertracing/jaeger-operator (infra) score 72

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:34.536359+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T16:56:46.571344+00:00, confidence not recorded.
  - readme: https://github.com/jaegertracing/jaeger (fetched 2026-08-28T04:11:34.536359+00:00, sha 37025393220e)
  - homepage: https://www.jaegertracing.io/ (fetched 2026-08-29T07:55:00.483086+00:00, sha 1f59da1539c8)
  - site_page: https://www.jaegertracing.io/docs/latest (fetched 2026-08-29T07:55:00.492260+00:00, sha 9ce70bfaaac6)
  - site_page: https://www.jaegertracing.io/docs/2.20/getting-started (fetched 2026-08-29T07:55:00.494164+00:00, sha 6216f8da5382)
- Data as of 2026-08-30T08:39:29.467469+00:00.