This project contains samples demonstrating the microservices tracing using zipkin.
spring cloud sleuth automatically instruments common communication channels:
- Requests over messaging technologies like Apache Kafka or RabbitMQ (or any other spring cloud stream binder)
- HTTP headers received at Spring MVC controllers
- Requests that pass through a Netflix Zuul microproxy
- Requests made with the RestTemplate, etc.
Distributed Tracing system to trace the request across services in microservices architecture.
Navigate to http://localhost:9411 to view Zipkin UI.
| Name | Port | Description |
|---|---|---|
| zipkin-ui-server | 9411 | Zipkin UI server |
| zipkin-client-1 | 8081 | Client application |
| zipkin-client-2 | 8082 | Client application |
- Download/Clone the repository :
$ git clone https://github.com/BarathArivazhagan/spring-cloud-zipkin-tracing && cd spring-cloud-zipkin-tracing
$ ./mvnw clean install
- To run the application :
$ docker-compose up
Navigate to http://localhost:8081/client Client 1 --> Client 2 interaction
Navigate to http://localhost:8082/client Client 2 --> Client 1 interaction
Navigate to http://localhost:8082/client Client 2 --> Client 1 interaction
2017-10-29 20:26:37.497 INFO [zipkin-client-1,9866ef627387f89d,9866ef627387f89d,true] 5025 --- [nio-8081-exec-8] com.barath.app.AppController : Invoke Client 1
2017-10-29 20:26:37.521 INFO [zipkin-client-2,9866ef627387f89d,353315ba5919a55d,true] 5029 --- [io-8082-exec-10] com.barath.app.AppController : Welcome Home from Client 2 is called
$ docker-compose build
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent