Distributed tracing in microservices
Follow a request end-to-end across multiple services to identify bottlenecks and understand dependencies.
Observabilité · Courses
Master the observability standard. Learn to instrument your applications, collect and export your traces, metrics and logs with OpenTelemetry.
LEARNING PATH
Understand the key components: the API, the SDK and the OTLP protocol.
The brain of your observability pipeline: configuring receivers, processors and exporters.
Learn to generate data with auto-instrumentation and manual instrumentation (SDK).
Details on handling and correlating the three pillars of observability.
A real-world scenario with Docker and Kubernetes.
LEARN BY DOING
Follow a request end-to-end across multiple services to identify bottlenecks and understand dependencies.
Use a unified log format across every application, regardless of language, and automatically enrich it with trace context.
Create business metrics (e.g. abandoned carts, revenue per minute) and export them to a system such as Prometheus or Mimir.
It's a standard and a set of open-source tools (API, SDK, Collector) for instrumenting, generating, collecting and exporting telemetry data (traces, metrics, logs).
It's OpenTelemetry's native protocol (OpenTelemetry Protocol) for transporting telemetry data efficiently and in a standardized way between the different components.
No, that's one of its major strengths. OTel is vendor-agnostic and can send data to many backends (Jaeger, Prometheus, Dynatrace, Datadog, etc.) via exporters, sparing you from vendor lock-in.