This is an example app where a web browser and two express (node.js) 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
This example was initially shown at DevOpsDays Singapore on Oct 8, 2016. It was ported from similar examples, such as Spring Boot.
Web requests are served by Express controllers, and tracing is automatically performed for you by zipkin-js. JavaScript used in the web browser is bundled with browserify.
This example has two services: frontend and backend. They both report trace data to zipkin. To setup the demo, you need to start frontend.js, backend.js and Zipkin. You'll also need to bundle the JavaScript used by the web browser.
Once the services are started, and the JavaScript is bundled, open index.html
- This starts a trace in the browser and calls the frontend (http://localhost:8081/)
- This continues the trace and calls 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=browser
- This is a locally run zipkin service which keeps traces in memory
Before you start anything, you'll need to download the libraries used in this demo:
$ npm installOnce that's done, bundle the JavaScript used by the browser:
$ npm run browserifyIn a separate tab or window, run npm start, which will start both frontend.js and backend.js:
$ npm startNext, run Zipkin, which stores and queries traces reported by the browser and above services.
$ wget -O zipkin.jar 'https://search.maven.org/remote_content?g=io.zipkin.java&a=zipkin-server&v=LATEST&c=exec'
$ java -jar zipkin.jarOr, if you're using docker:
$ docker run -d -p 9411:9411 openzipkin/zipkin