Files

Marcin Grzejszczak 358d0b16b5 Issues #286 custom feign config (#289 )

After this change a custom FeignContext is created that before returning instance  or instances of beans will wrap, if necessary, that bean into a tracing representation. That way all the custom Feign configurations will have wrapped beans and tracing will get propagated.

Fixes #286

2016-05-25 18:12:06 +02:00

src

Issues #286 custom feign config (#289 )

2016-05-25 18:12:06 +02:00

docker-compose.yml

Removed docker compose

2016-04-04 14:40:22 +02:00

pom.xml

Moves to zipkin 0.21

2016-05-23 11:21:53 -04:00

README.md

Moves to zipkin 0.21

2016-05-23 11:21:53 -04:00

README.md

Running a Zipkin Server

There are 3 parts to Zipkin:

the instrumented client apps
the backend database (defaults to in-memory db)
the Zipkin server

Zipkin Services

Run the Zipkin (remember to have RabbitMQ running) by

either running Spring Boot Maven plugin:

./mvnw spring-boot:run --projects spring-cloud-sleuth-samples/spring-cloud-sleuth-sample-zipkin-stream

or running the packaged app from the root:

./mvnw package --projects spring-cloud-sleuth-samples/spring-cloud-sleuth-sample-zipkin-stream
java -jar spring-cloud-sleuth-samples/spring-cloud-sleuth-sample-zipkin-stream/target/spring-cloud-sleuth-sample-zipkin-stream-1.0.0.BUILD-SNAPSHOT-exec.jar

and test it

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

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