Example: Skaffold Command Tracing with Jaeger

WARNING: Skaffold's trace functionality is experimental and may change without notice.

In this example:

• Use Skaffold to deploy a local/remote Jaeger instance
• Enable Skaffold tracing functionality to get trace information about skaffold dev, build, deploy, etc. timings
• Send Skaffold trace information to Jaeger and have that information be visible in the Jaeger UI,

In this example, we'll walk through enabling Skaffold trace information that can be used to explore performance bottlenecks and to get a more in depth view of user's local dev loop.

WARNING: If you're running this on a cloud cluster, this example will create a service and expose a webserver. It's highly recommended that you only run this example on a local, private cluster like minikube or Kubernetes in Docker for Desktop.

Setting up Jaeger locally

Use docker to start a local jaeger instance using the Jaeger project's all-in-one docker setup:

docker run -d --name jaeger \
  -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \
  -p 5775:5775/udp \
  -p 6831:6831/udp \
  -p 6832:6832/udp \
  -p 5778:5778 \
  -p 16686:16686 \
  -p 14268:14268 \
  -p 14250:14250 \
  -p 9411:9411 \
  jaegertracing/all-in-one:1.22

Now, in a different terminal, go to another Skaffold example (eg: microservices), enable SKAFFOLD_TRACE with Jaeger and start dev session there:

cd ../microservices
export SKAFFOLD_TRACE=jaeger
skaffold dev

Now go to the Jaeger UI that Skaffold will port-forward to localhost at http://127.0.0.1:16686/

Select service:skaffold-trace in the left bar and then click Find Traces on the bottom of the left bar.

From here you should be able to view all of the relevant traces

Cleaning up

To cleanup Jaeger all-in-one setup, run the following:

docker kill jaeger # stops the running jaeger container
docker rm jaeger #removes the container image