June 2026
Intermediate
490 pages
10h 47m
English
In Chapter 3, we saw how println! logging and manual correlation IDs leave us blind to timing and causality across service boundaries. They tell us what happened, but not where the time went.
This chapter bridges that gap. We will integrate OpenTelemetry into our Rust services to capture timing information at every service boundary. By the end, every HTTP request flowing through OtelMart, Products, Inventory, and Orders will automatically generate connected traces, complete with timing information, service boundaries, and causal relationships, without requiring manual propagation of correlation IDs.
We will build what we call the telemetry skeleton: the foundational infrastructure that makes every ...
Read now
Unlock full access