Distributed Tracing with Zipkin in Istio

7th chunk of `content/en/blog/_posts/2017-05-00-Managing-Microservices-With-Istio-Service-Mesh.md`

7ef80561785bc8e2cab946a88249c03fc30178629f64dc36000000010000030d

![istio-dashboard-k8s-blog.png](https://lh5.googleusercontent.com/yFBKYWEmNxs-8VLtlJIG4BV0dUzqrvCfhWLh2CrGHyTtH5dArQy-owua3vdMCSjkdjtk8E3ZmEz32EupRL28WHALLm9MqJwCJrs1N5yv8typUJiLS_ExsO-uleaZ3bgbPraC8lgi)



**Distributed tracing**  The next thing we get from Istio is call tracing with Zipkin. We obtain its NodePort URL:  


 ```
export ZIPKIN\_URL=$(kubectl get po -l app=zipkin -o jsonpath={.items[0].status.hostIP}):$(kubectl get svc zipkin -o jsonpath={.spec.ports[0].nodePort})
  ```


We can now point a browser at http://$ZIPKIN\_URL/ to see request trace spans through the Bookinfo services.  


 ![](https://lh4.googleusercontent.com/qfm6Jobqaw9J6sdeG93rXb9KYb39DoVKJ0fqKFQiyi5JVEfiypAbvAOBw8OTPOgnAnv3TzDEripkOw9xCJLrwbE7jJziU_tHoyS8CFeVrGG_X0Ut1oV0OyUCB8Xo4U8UGNgm-7Ve)

Title: Distributed Tracing with Zipkin in Istio

Summary

Istio provides call tracing with Zipkin. The NodePort URL for Zipkin is obtained using `kubectl`. By accessing this URL in a browser, request trace spans through the Bookinfo services can be visualized, allowing for distributed tracing.