Files
spring-cloud-sleuth/spring-cloud-sleuth-samples/spring-cloud-sleuth-sample-zipkin-stream
Adrian Cole eaa008f933 Updates to zipkin 0.11
The only notable change for Sleuth is an artifact id change from
spanstore to storage.
2016-04-03 21:04:55 +08:00
..
2016-03-31 19:31:45 +08:00
2016-04-03 21:04:55 +08:00

Running a Zipkin Server

There are 3 parts to Zipkin: the instrumented client apps, the backend database and the Zipkin server. The database for this implementation is MySQL.

Zipkin Services

Run this app using the docker-compose provided.

$ docker-compose build zipkin
$ docker-compose up
...

and test it

$ curl localhost:9411/api/v1/services
["zipkin-query"]

The app might fail to start if mysql is not available when it needs it. If that happens you can just start it separately: just keep running docker-compose up until it works.

Instrumenting Apps

Depend on Spring Cloud Sleuth Stream and the rabbit binder (spring-cloud-starter-stream-rabbit).

Once the apps start publishing spans they will appear in the span store as well.

Running in an IDE

You can run this app in an IDE and still use docker-compose to create the middleware:

$ docker-compose up rabbitmq mysql