April 2018
Intermediate to advanced
432 pages
10h 38m
English
Integration with Zipkin via HTTP is not the only option. As is usual with Spring Cloud, we may use a message broker as a proxy. There are two available brokers—RabbitMQ and Kafka. The first of these can be included in the project by using the spring-rabbit dependency, while the second can be included with spring-kafka. The default destination name for both of these brokers is zipkin:
<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-zipkin</artifactId></dependency><dependency> <groupId>org.springframework.amqp</groupId> <artifactId>spring-rabbit</artifactId></dependency>
This feature also requires changes on the Zipkin server side. We have configured a consumer that is ...