This example shows how to use Camel with Zipkin to trace/timing all incoming and outgoing Camel messages.

The example requires a running Zipkin Server.

The example includes three sub maven modules that implement

• client

• service1

• service2

Where client → service1 → service2 using HTTP.

This example assumes you will run Zipkin on the same host using the default collector port of 9410. If you wish to change those, you can do so using these files:

Service1 is configured in the src/main/resources/application.properties properties file. Service2 is configured in the src/main/java/sample/camel/Service2Route.java source file. Client is configured in the src/main/java/sample/camel/ClientApplication.java source file.

First, start Zipkin as described below in the Installing Zipkin Server section

Then compile this example:

Then using three different shells and run service1 and service2 before the client.

When service1 is ready then start service2

And then start the client that calls service1 every 30th seconds.

You should be able to visualize the traces and timings from this example using the Zipkin UI. The services are named service1 and service2.

In the screen shot below we are showing a trace of a client calling service1 and service2.

You can then click on each span and get annotated data from the Camel exchange and about the requests as shown:

The quickest way to get Zipkin started is to fetch the latest released server as a self-contained executable jar.

1. and then run it

Finally, browse to http://localhost:9411 to find traces!

If you want to try Zipkin locally then you quickly try that using Docker.

There is a quickstart guide at zipkin that has further instructions. Remember to configure the IP address and port number in the application.properties file.

You can find the IP using docker-machine ls

If you hit any problem using Camel or have some feedback, then please let us know.

We also love contributors, so get involved :-)

The Camel riders!