Advanced Spring Boot 4: Event-Driven Architecture (Kafka) · 강의

Sleuth/Zipkin을 활용한 분산 추적

Spring Cloud Sleuth와 Zipkin을 사용해 여러 마이크로서비스를 가로지르는 이벤트 흐름을 추적하는 분산 추적을 구현합니다.

Sleuth/Zipkin을 활용한 분산 추적은(는) CoddyKit의 무료 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

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.0

Tracing 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 @KafkaListener receives 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/zipkin

Producer 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!

자주 묻는 질문

“Sleuth/Zipkin을 활용한 분산 추적” 강의는 무료인가요?

네 — “Sleuth/Zipkin을 활용한 분산 추적” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의 전체를 잠금 해제할 수 있습니다. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에는 총 4개의 강의가 포함되어 있습니다.

“Sleuth/Zipkin을 활용한 분산 추적”에서 뭘 배우나요?

Spring Cloud Sleuth와 Zipkin을 사용해 여러 마이크로서비스를 가로지르는 이벤트 흐름을 추적하는 분산 추적을 구현합니다. 브라우저에서 직접 실행하는 실습 코드로 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Advanced Spring Boot 4: Event-Driven Architecture (Kafka)을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.

“Sleuth/Zipkin을 활용한 분산 추적” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Advanced Spring Boot 4: Event-Driven Architecture (Kafka)(으)로 돌아가기