Basic example showing distributed tracing across Armeria apps

This is an example app where two Armeria (Java) services collaborate on an http request. Notably, timing of these requests are recorded into Zipkin, a distributed tracing system. This allows you to see the how long the whole operation took, as well how much time was spent in each service.

Here's an example of what it looks like

Implementation Overview

Web requests are served by Armeria services, which trace requests by using the Zipkin plugin.

These traces are sent out of process over http to Zipkin.

This example intentionally avoids advanced topics like async and load balancing, eventhough Armeria supports them.

Running the example

This example has two services: frontend and backend. They both report trace data to zipkin. To setup the demo, you need to start Frontend, Backend and Zipkin.

Once the services are started, open http://localhost:8081/

• This will call the backend (http://localhost:9000/api) and show the result, which defaults to a formatted date.

Next, you can view traces that went through the backend via http://localhost:9411/?serviceName=backend

• This is a locally run zipkin service which keeps traces in memory

Starting the Services

In a separate tab or window, start each of armeria.Frontend and armeria.Backend:

$ ./mvnw compile exec:java -Dexec.mainClass=armeria.Frontend
$ ./mvnw compile exec:java -Dexec.mainClass=armeria.Backend

Next, run Zipkin, which stores and queries traces reported by the above services.

curl -sSL https://zipkin.io/quickstart.sh | bash -s
java -jar zipkin.jar