Jaeger is an open-source tool that helps developers monitor the performance and availability of their microservices. It provides insights into traffic and interactions between services to identify bottlenecks and optimization opportunities.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Usable application software: supports people in a task.
Concrete cog in the system that works inside larger relationships.
Jaeger is an open-source distributed-tracing system that captures and analyzes the path of individual requests through distributed services.
Uber developed Jaeger from 2015 for microservice observability, released it as open source, and later contributed it to the Cloud Native Computing Foundation.
Instrumented services create spans with trace ID, timing, attributes, and relationships. Collectors receive and store them; the query service and UI reconstruct the trace. Sampling limits data volume, while OpenTelemetry standardizes collection.
Time-bounded operations form the smallest units of a distributed flow.
Propagated IDs connect operations across process and service boundaries.
Timelines and dependencies expose latency, errors, and critical paths.
Jaeger supports root-cause analysis and performance understanding in distributed systems. Its value depends on complete context propagation, meaningful instrumentation, sampling strategy, privacy, and controlled cardinality.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.