Jaeger OpenTracing

The OpenTracing API provides a standard, vendor neutral framework for instrumentation. This means that if a developer wants to try out a different distributed tracing system, then instead of repeating the whole instrumentation process for the new distributed tracing system, the developer can simply change the configuration of the Tracer.

Please visit OpenTracing site for more information.

There are numeric tracers implement OpenTracing API and one of them is CNCF Jaeger. In this tutorial, we are going to walk you the steps to leverage Jaeger with a distributed light-4j application.

In light-4j, we have a new module called jaeger-tracing added with a JaegerStartupHookProvider to init the tracer and a JaegerHandler to extract the Tracing context and start the Span and finish the Span.

The client module is also modified to add two more public method to inject the tracing context to the next service in the request.

Service Discovery

In the previous step, we have instrumented the OpenAPI petstore application and walked through the Jaeger UI. When talking about distributed tracing, we need to pass the context from one service to another service. If you remember, we have the service discovery tutorial with four services calling each other. We are going to extend it with OpenTracing so that users can see how the original request flows through multiple services. We can also add a standalone client to invoke the api_a and pass in a tracing context. Read More »

Petstore Jaeger

In the previous step, we have started the all-in-one Jaeger. You can see that there is only one service registered as jaeger-query on the UI. In this step, we are going to change the configuration of petstore to enable jaeger-tracing. petstore First, let’s make sure that the petstore application is working in the light-example-4j. If you haven’t checked out the light-example-4j, please do so. cd ~/networknt git clone https://github.com/networknt/light-example-4j.git cd light-example-4j mvn clean install exec:exec The server should be up and running now. Read More »

All in One

Your applications must be instrumented before they can send tracing data to Jaeger backend. Before that, we need to start the tracer. All-in-one is an executable designed for quick local testing, launching the Jaeger UI, collector, query, and agent, with an in-memory storage component. The simplest way to start the all-in-one is to use the pre-built image published to DockerHub (a single command line). docker run -d --name jaeger \ -e COLLECTOR_ZIPKIN_HTTP_PORT=9411 \ -p 5775:5775/udp \ -p 6831:6831/udp \ -p 6832:6832/udp \ -p 5778:5778 \ -p 16686:16686 \ -p 14268:14268 \ -p 9411:9411 \ jaegertracing/all-in-one:1. Read More »