8382a823e5
This updates to the latest release. Beyond bug fixes, there are some notable changes: * storage: writes are now via AsyncSpanConsumer * storage: added elasticsearch * zipkin-ui: constrains start time to look for traces * zipkin-ui: assets set cache headers, increasing responsiveness * core: debug logging available for zipkin.internal.DependencyLinker
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