Example implementation of multi application tracking with jaeger tracing.
This project has 3 different applications,
api-a
, is simple NodeJs app called Service Aapi-b
, is simple NodeJs app called Service Bapi-c
, is simple Golang app called Service C
In operation, the Service A is depends on Service B and C, mimicking microservices architecture, so then you'll get the idea about how opentracing works in practice using Jaeger as a backend.
- Make sure your environment already setup for NodeJs and Go (with go module support)
- Clone this repository
git clone --depth=1 git@github.com:slaveofcode/jaeger-multi-app-tracking-example.git
- Start Service A by go to
api-a
directory and run commandnpm start
, the same steps applied to Service B onapi-b
- Start Service C by go to
api-c
directory and run commandgo run server.go
- Run the Jaeger
jaeger-all-in-one
binary, to start agent, collector and query server just from that single binary, or you can using its Docker image as described here. - Start making some requests by hitting http://localhost:8110/api/users and http://localhost:8110/api/users/1
- Visit Jaeger UI at http://localhost:16686 and select Service A on the Filter Search box to see some traces.
MIT License
Copyright (c) 2020 Aditya Kresna
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.