Jaeger - Distributed Tracing for Cloud Native Applications

• Distributed tracing, monitoring using Jaeger
• Installation, Setup and Configuration of Jaeger for distributed tracing
• Troubleshoot transactions in complex distributed systems
• Performance and latency optimization of distributed applicatiions
• Root cause and service dependency analysis of distributed applications
• Distributed context propagation

Solve the major operation problem of distributed applications in networking and observability

Learn the following skills on distributed applications

• Distributed transaction monitoring

• Performance and latency optimization

• Root cause analysis

• Service dependency analysis

• Distributed context propagation

Learn various components in Jaeger like

• Jaeger UI

• Collector

• Query

• Agent

• Jaeger-ingester

• In-memory Storage

Deploy and use all-in-one open telemetry application for learning purpose

Using Jaeger configuration along with OpenTelemetry configuration

Jager API and its architecture

Sampling and its importance

Learn different terminologies like

Span: The basic unit of work in tracing, representing a single operation within a trace, including details like operation name, start and end times, logs, and tags.

Trace: A collection of spans that share the same trace ID, representing a complete end-to-end execution path across services.

Components: Different parts of the Jaeger architecture, including the agent, collector, query service, and storage backends, each responsible for a specific role in the tracing pipeline.

Jaeger Client Libraries: Language-specific libraries provided by Jaeger that allow applications to create and manage spans and traces, supporting languages like Go, Java, Node.js, Python, C++, and C#.

Agent: A lightweight process that listens for span data sent by client libraries and forwards it to the Jaeger collector.

Collector: The backend component that receives span data from agents, processes it, and stores it in the chosen storage system.

Query: The service that provides APIs and a user interface for searching and visualizing trace data stored by the collector.

Ingester: A component used when storing spans in streaming or scalable storage backends (like Kafka), responsible for consuming spans and writing them to permanent storage.

Using different client libraries and languages like Go, Java, Node.js, Python, C++, C#

Performance tuning and troubleshooting

Monitoring Jaeger and its different component