Tracing distribuito con Sleuth/Zipkin
Implementi il tracing distribuito usando Spring Cloud Sleuth e Zipkin per seguire i flussi degli eventi attraverso più microservizi.
Tracing distribuito con Sleuth/Zipkin è una lezione Advanced Spring Boot 4: Event-Driven Architecture (Kafka) gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Advanced Spring Boot 4: Event-Driven Architecture (Kafka), e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Advanced Spring Boot 4: Event-Driven Architecture (Kafka) include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Why Trace Distributed Systems?
In a microservices architecture, a single user request often travels through many different services. This distributed nature makes it incredibly hard to track the flow of requests and pinpoint where issues occur.
Distributed tracing helps you visualize the full journey of a request across all services involved, making debugging and performance monitoring much easier.
Trace and Span: Your Navigation Tools
Distributed tracing relies on two core concepts:
- Trace: Represents the complete journey of a request through a system, from start to finish. It's like a story of one operation.
- Span: A single, logical unit of work within a trace. Each operation (e.g., an HTTP request, a database call, sending a Kafka message) gets its own span. Spans have parent-child relationships, showing cause and effect.
Meet Spring Cloud Sleuth
Spring Cloud Sleuth is a powerful library for Spring Boot applications that automatically adds distributed tracing capabilities. It instruments your application to generate, collect, and propagate trace information.
- It automatically adds trace and span IDs to your logs.
- It propagates these IDs across service boundaries (HTTP, messaging, etc.).
This means you don't have to manually manage trace IDs in most cases!
Getting Started: Add Sleuth & Zipkin
To integrate Spring Cloud Sleuth into your Spring Boot project, add the following dependencies to your pom.xml:
spring-cloud-starter-sleuth: The core tracing library.spring-cloud-sleuth-zipkin: Integrates with Zipkin for trace visualization.
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-sleuth</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-sleuth-zipkin</artifactId>
</dependency>Minimal Sleuth Configuration
After adding the dependencies, a minimal configuration in your application.properties is usually enough to get started. Sleuth will automatically detect and configure itself.
To send traces to a Zipkin server, specify its URL:
spring.application.name=my-kafka-producer-app
spring.zipkin.base-url=http://localhost:9411
spring.sleuth.sampler.probability=1.0Tracing Across Kafka Messages
One of Sleuth's key features is its ability to propagate trace context across messaging systems like Kafka. When you use Spring's KafkaTemplate to send messages:
- Sleuth automatically injects trace and span IDs into the Kafka message headers.
- When a
@KafkaListenerreceives the message, Sleuth extracts these headers and continues the trace, linking the producer's span to the consumer's span.
This creates a continuous trace, even across asynchronous Kafka message flows.
Zipkin: See Your Traces
While Sleuth generates and propagates trace data, Zipkin is the distributed tracing system that collects, stores, and visualizes this data. It provides a user interface where you can:
- Search for traces by service name, timestamp, or trace ID.
- View a Gantt chart representation of a trace, showing the sequence and duration of spans.
- Identify performance bottlenecks and errors across your microservices.
Spin Up Zipkin Locally
For local development and testing, you can easily run a Zipkin server using Docker. This provides a quick way to see your traces without complex setup.
docker run -d -p 9411:9411 openzipkin/zipkinProducer with Sleuth Instrumentation
Here's a simple Spring Boot Kafka producer. With Sleuth and Zipkin configured (as shown in earlier scenes), when you run this, Sleuth will automatically add tracing headers to the Kafka message. You would see the traceId and spanId in your application logs and in the Zipkin UI.
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.core.KafkaTemplate;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestParam;
import org.springframework.web.bind.annotation.RestController;
@SpringBootApplication
@RestController
public class SleuthKafkaProducerApplication {
@Autowired
private KafkaTemplate<String, String> kafkaTemplate;
private static final String TOPIC = "my-traceable-topic";
public static void main(String[] args) {
SpringApplication.run(SleuthKafkaProducerApplication.class, args);
}
@GetMapping("/send")
public String sendMessage(@RequestParam("message") String message) {
kafkaTemplate.send(TOPIC, message);
return "Message sent with trace context: " + message;
}
}Quick Check: Tracing Concepts
When a Spring Boot application with Spring Cloud Sleuth sends a message to Kafka, which of the following statements are true about trace information?
Lesson Summary: Tracing Your Flow
You've learned about distributed tracing, a critical technique for understanding complex microservice interactions. We covered:
- The concepts of Trace (full request journey) and Span (individual operation).
- How Spring Cloud Sleuth automatically instruments Spring Boot applications, including Kafka producers and consumers, to propagate tracing context.
- The role of Zipkin in collecting and visualizing these traces, providing invaluable insights into your system's behavior.
With these tools, you can effectively monitor and debug your event-driven microservices!
Domande Frequenti
La lezione «Tracing distribuito con Sleuth/Zipkin» è gratuita?
Sì — il testo completo di «Tracing distribuito con Sleuth/Zipkin» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Advanced Spring Boot 4: Event-Driven Architecture (Kafka), passa a CoddyKit PRO. Il corso Advanced Spring Boot 4: Event-Driven Architecture (Kafka) include 4 lezioni in totale.
Cosa imparerò in «Tracing distribuito con Sleuth/Zipkin»?
Implementi il tracing distribuito usando Spring Cloud Sleuth e Zipkin per seguire i flussi degli eventi attraverso più microservizi. Eserciti Advanced Spring Boot 4: Event-Driven Architecture (Kafka) con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?
Non è richiesta alcuna esperienza precedente. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Tracing distribuito con Sleuth/Zipkin»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione Advanced Spring Boot 4: Event-Driven Architecture (Kafka)?
Sì. Ogni lezione Advanced Spring Boot 4: Event-Driven Architecture (Kafka) include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Metriche Kafka (JMX) e controlli dello stato
- Integrazione con Prometheus e Grafana
- Tracing distribuito con Sleuth/Zipkin
- Monitorare il consumer lag e configurare gli alert