I want to finish off this chapter with another form of integration of tracing and a service mesh, where we use distributed context propagation of the tracing API to affect the routing of the requests. To run the example, please revert the change to the pom.xml
files to add back the Jaeger tracer dependencies. Then rebuild and redeploy the application:
$ make delete-app $ make build-app $ make deploy-app $ kubectl get pods
As you may remember, I mentioned earlier in this chapter that we deploy two versions of the formatter
service, v1 and v2, where v2 is passed an extra environment variable, professor=true
. That version produces a different response, but we have not seen it yet. In order to get it, we need to take a walk down memory lane. In the early days of the internet, there used to be a great web browser called Netscape. One has to be very old, like the Professor, to remember it. What if we pretend to send a request from that browser?
$ curl -A Netscape...