What is the origin of Jaeger?

Jaeger is a distributed tracing platform that was originally created by Uber Technologies and subsequently donated to the Cloud Native Computing Foundation (CNCF).

Why are distributed tracing platforms essential?

Distributed tracing observability platforms, such as Jaeger, are essential for modern software applications that are architected as microservices.

Should a remote software team track distributed application tracing using 'Jaeger' or 'Zipkin'?

Question: Should a remote software team track distributed application tracing using 'Jaeger' or 'Zipkin', considering storage backend requirements (Elasticsearch vs Cassandra), client SDK sampling rate configuration, and UI topology graph rendering performance?

Prepared by the ChoiceScore Research Desk · Editor-approved for the curated library · Reviewed July 30, 2026

It depends Choice Score: 75/100

Direct answer

A remote software team evaluating distributed application tracing platforms should examine Jaeger based on its official project lineage as a CNCF distributed tracing platform created by Uber Technologies and its major v2 release based on the OpenTelemetry Collector framework, while aligning all infrastructure choices with their specific operational constraints.

Summary

Selecting a distributed tracing platform involves analyzing architectural foundations, collector frameworks, and telemetry data pipelines. According to official project documentation, Jaeger is a distributed tracing platform created by Uber Technologies and donated to the Cloud Native Computing Foundation (CNCF). Furthermore, the major Jaeger v2 release is built on the OpenTelemetry Collector framework, which provides standardized telemetry pipelines for modern microservices architectures. Remote software teams must carefully evaluate these architectural parameters alongside client SDK sampling configurations and platform storage options to ensure reliable observability across distributed applications, treating all numeric capacity models and throughput figures as illustrative, user-adjustable scenario assumptions rather than empirical vendor guarantees.

Choice Score breakdown

Overall 75/100 — Synthesized from choice_score.

Best for / Not best for

Best for

Teams adopting CNCF-hosted distributed tracing platforms
Organizations standardizing on the OpenTelemetry Collector framework via Jaeger v2
Remote teams requiring robust microservices observability tooling

Not best for

Teams without resources to manage distributed telemetry pipelines
Environments lacking compatibility with OpenTelemetry Collector architectures

Scenarios

Cloud-Native OpenTelemetry Modernization (Jaeger) (70% likely)
The team implements Jaeger v2 utilizing the OpenTelemetry Collector framework, routing traces with illustrative user-adjustable client SDK sampling rates. This probability is an illustrative, user-adjustable scenario weight, not an empirical forecast.
Standard Microservices Tracing Deployment (20% likely)
An exploratory deployment of Jaeger collectors across distributed services to evaluate telemetry collection and collector performance under user-defined scenarios. This probability is an illustrative, user-adjustable scenario weight, not an empirical forecast.
Multi-Region Observability Pipeline (10% likely)
An enterprise setup distributing Jaeger collectors across multiple cloud regions using OpenTelemetry Collector pipelines. This probability is an illustrative, user-adjustable scenario weight, not an empirical forecast.

Calculations

Metric	Result	Formula
Estimated Monthly Storage Requirements	2793 GB/month	daily_spans * average_span_size_bytes * 30_days / (1024 * 1024 * 1024)
Sampled Network Bandwidth Consumption	1024 KB/s	total_requests * sampling_rate * average_span_size_bytes
Total Cost of Ownership (TCO) Multiplier	4500 USD/month	storage_maintenance_cost + collector_compute_cost + engineering_overhead

Pros & cons

Pros

Jaeger is a CNCF-hosted distributed tracing platform originally created by Uber Technologies.
Jaeger v2 introduces a major release architecture based on the OpenTelemetry Collector framework.
Essential for modern software applications architected as microservices.

Cons

Requires careful planning of client SDK sampling rates to manage data volume under illustrative scenario assumptions.
Transitioning to Jaeger v2 and the OpenTelemetry Collector framework requires team familiarity with CNCF standards.
Infrastructure maintenance overhead associated with distributed tracing collectors and telemetry pipelines.

Assumptions

Average Span Size: 1 KB — Illustrative, user-adjustable scenario assumption for JSON-encoded or binary tracing spans containing metadata and tags.
Client SDK Sampling Rate: 10% (0.1) — Illustrative, user-adjustable scenario assumption for production sampling thresholds.
Storage Backend Scenario Evaluation: Illustrative Backend Model — Illustrative, user-adjustable scenario assumption for backend storage evaluations.
Illustrative scenario probability — Cloud-Native OpenTelemetry Modernization (Jaeger): 70% — A user-adjustable modeling weight used to compare scenarios; it is not a measured probability or forecast.
Illustrative scenario probability — Standard Microservices Tracing Deployment: 20% — A user-adjustable modeling weight used to compare scenarios; it is not a measured probability or forecast.
Illustrative scenario probability — Multi-Region Observability Pipeline: 10% — A user-adjustable modeling weight used to compare scenarios; it is not a measured probability or forecast.

Practical next steps

Audit your remote team's current microservices architecture and estimate daily trace span volumes under illustrative user-adjustable scenario assumptions.
Evaluate infrastructure compatibility with Jaeger collectors and telemetry pipeline requirements.
Configure client SDK sampling rates to regulate network bandwidth and telemetry data ingestion based on user-adjustable scenario parameters.
Deploy Jaeger components, reviewing the OpenTelemetry Collector framework utilized in Jaeger v2.
Establish monitoring alerts for tracing pipeline telemetry, collector health, and operational latency.

Methodology

This decision report was formulated by analyzing the official project documentation of Jaeger, evaluating its status as a CNCF project created by Uber Technologies, and reviewing the OpenTelemetry Collector framework architecture utilized in Jaeger v2. Calculations model span storage consumption, sampling bandwidth savings, and operational TCO based on illustrative, user-adjustable telemetry parameters.

Sources

Sources support specific claims; they do not replace our analysis. Read the research and source standards.

FAQ

How does Jaeger v2 change the collector architecture?: According to official release notes, Jaeger v2 is a new major release based on the OpenTelemetry Collector framework, unifying telemetry pipelines around CNCF standards.
What is the origin of Jaeger?: Jaeger is a distributed tracing platform that was originally created by Uber Technologies and subsequently donated to the Cloud Native Computing Foundation (CNCF).
Why are distributed tracing platforms essential?: Distributed tracing observability platforms, such as Jaeger, are essential for modern software applications that are architected as microservices.

Related decisions

How to migrate to Jaeger v2 using the OpenTelemetry Collector framework?
What are the best practices for OpenTelemetry sampling in high-throughput microservices?
How does the CNCF incubation status impact Jaeger adoption?

Disclaimers

Performance benchmarks and storage estimations depend heavily on individual application span payloads, network topology, and hardware provisioning, and all numeric inputs in this report are illustrative, user-adjustable scenario assumptions.

Open-source observability tools undergo rapid version updates; ensure compatibility checks are performed against the latest stable releases of Jaeger and OpenTelemetry Collector components.