0Pricing
Spring Boot 4 Microservices & REST APIs · Aula

Rastreamento distribuído com Zipkin

Integre o Zipkin para rastrear ponta a ponta microsserviços distribuídos e depurar interações complexas.

Rastreamento distribuído com Zipkin é uma aula grátis de Spring Boot 4 Microservices & REST APIs no CoddyKit. Esta é a aula 3 de 3. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Spring Boot 4 Microservices & REST APIs, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Spring Boot 4 Microservices & REST APIs inclui 3 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

The Microservice Debugging Maze

In a microservices architecture, a single user request might travel through many different services. When something goes wrong, it's like finding a needle in a haystack!

Traditional logging only shows what happened within one service. We need a way to see the entire journey.

What is Distributed Tracing?

Distributed tracing is a technique to monitor and observe requests as they flow through different components of a distributed system.

  • It helps you understand how services interact.
  • It pinpoints performance bottlenecks.
  • It makes debugging across service boundaries much easier.

Introducing Zipkin

Zipkin is an open-source distributed tracing system.

It helps you gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data.

Core Concepts: Trace & Span

Two fundamental concepts in distributed tracing are Traces and Spans:

  • A Trace represents a single request or workflow as it flows through your entire system.
  • A Span is a single operation within a trace. It has a name, a unique ID, and a parent ID (unless it's the root span).

Think of a Trace as a story, and Spans as the individual chapters.

How Zipkin Works

Zipkin works by collecting data from your instrumented services.

Here's the basic flow:

  1. Your services send tracing data (spans) to the Zipkin Collector.
  2. The Collector stores this data (e.g., in memory, MySQL, Elasticsearch).
  3. You use the Zipkin UI to visualize and analyze the traces.

Spring Cloud Sleuth Magic

For Spring Boot applications, Spring Cloud Sleuth makes integration with Zipkin incredibly easy.

Sleuth automatically adds tracing information to your logs and HTTP headers, and sends it to Zipkin without much manual coding from you.

Setting Up Zipkin Locally

The easiest way to run a Zipkin server locally is using Docker. If you have Docker installed, just run this command in your terminal:

docker run -p 9411:9411 openzipkin/zipkin

Once running, you can access the Zipkin UI at http://localhost:9411.

Simple Service Instrumentation

To enable tracing, add Sleuth and Zipkin dependencies (spring-cloud-starter-sleuth and spring-cloud-sleuth-zipkin). Then, configure your application.properties to point to the Zipkin server:

spring.application.name=my-traced-service
spring.zipkin.base-url=http://localhost:9411
spring.sleuth.sampler.probability=1.0 (trace all requests)

Now, let's look at a simple service that sends traces!

Tracing an Endpoint Call

Here's a basic Spring Boot service. With the properties from the last scene and Sleuth dependencies, it will automatically send trace data to Zipkin when you hit its /hello endpoint.

Try running this and then visiting http://localhost:8080/hello. Check your Zipkin UI!

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@SpringBootApplication
@RestController
public class MyTracedServiceApplication {

    public static void main(String[] args) {
        SpringApplication.run(MyTracedServiceApplication.class, args);
    }

    @GetMapping("/hello")
    public String hello() {
        // Sleuth automatically adds tracing to this request
        System.out.println("Processing /hello request...");
        return "Hello from Traced Service!";
    }
}

Exploring the Zipkin UI

After making requests to your traced service, open http://localhost:9411 in your browser.

You can search for traces by service name or trace ID. The UI will show you a visual timeline of each trace, including its spans, duration, and dependencies between services.

Quick Check: Tracing Terms

Test your understanding of distributed tracing with Zipkin.

Recap: Debugging with Zipkin

Great job! You've learned how distributed tracing helps debug microservices, and how Zipkin and Spring Cloud Sleuth make it easy.

  • Distributed tracing visualizes request flow.
  • Zipkin collects and displays trace data.
  • Sleuth automates instrumentation for Spring Boot.

This helps you quickly find issues and optimize performance across your services.

Perguntas Frequentes

A aula “Rastreamento distribuído com Zipkin” é grátis?

Sim — o texto completo de “Rastreamento distribuído com Zipkin” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Spring Boot 4 Microservices & REST APIs, atualize para CoddyKit PRO. O curso de Spring Boot 4 Microservices & REST APIs inclui 3 aulas no total.

O que vou aprender em “Rastreamento distribuído com Zipkin”?

Integre o Zipkin para rastrear ponta a ponta microsserviços distribuídos e depurar interações complexas. Você pratica Spring Boot 4 Microservices & REST APIs com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Spring Boot 4 Microservices & REST APIs?

Nenhuma experiência prévia é necessária. Spring Boot 4 Microservices & REST APIs no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 3.

Quanto tempo leva a aula “Rastreamento distribuído com Zipkin”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Spring Boot 4 Microservices & REST APIs?

Sim. Cada aula de Spring Boot 4 Microservices & REST APIs inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Disjuntores com Resilience4j
  2. Implementando alternativas e tempos limite
  3. Rastreamento distribuído com Zipkin
← Voltar para Spring Boot 4 Microservices & REST APIs