Distributed tracing is now a must-have feature in distributed system. OpenStack is not out of the loop in this wave. With traceability, devs/ops can quickly find performance bottleneck and root cause of issues in system.
In OpenStack, we have OSprofiler - a small library that act like a tracing tool for many internal OpenStack services (from Nova, Neutron, Keystone, Glance, Cinder,...).
However, with the rise of CNCF OpenTracing, there are a lot of chances for OSprofiler to evolve to a `more` standard and great tool for us to trouble-shoot OpenStack services.
OpenTracing is an open distributed tracing standard for applications. OpenTracing allows developers of application code, OSS packages, and OSS services to instrument their own code without binding to any particular tracing vendor.
In this talk, we introduce how we implementing OpenTracing standard into OSprofiler and how they work flawlessly. Live demos with Uber Jaeger and Zipkin at the end will illustrate this work.
- How OpenStack can collaborate with CNCF in term of distributed tracing
- A native and standard distributed tracing library for OpenStack services
- Multiple way to trace OpenStack service without vendor lock-in