advanced~2.5h

Distributed Tracing & Centralized Logging

One request that touches five services produces five separate sets of logs, on five separate machines. This module is how to make that feel like ONE trace again.

Learning objectives

  • Beginner: Explain what a trace ID is and why it needs to survive a call from one service to another.
  • Intermediate: View a distributed trace across multiple services in Zipkin.
  • Advanced: Correlate a slow trace span back to the specific log lines it produced, across two different services.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.

Distributed Tracing & Centralized Logging

Next Step

Continue to Distributed Transactions: Why 2PC Fails at Scale← Back to all Spring Cloud chapters