The OpenTracing API provides a standard, vendor-neutral framework for instrumentation of your code. It consists of an API specification, frameworks, and libraries that have implemented the specification. Once you’ve instrumented your code by creating spans for individual operations and then connecting them into traces throughout your system, Lightstep can show you how your system is running, where there may be issues, and where there may be opportunities to greatly improve performance.

Want to use OpenTelemetry instead? Read these docs to get started!

Already using Jaeger or Zipkin for tracing? Then your instrumentation is already done! Lightstep can ingest data from the Jaeger and Zipkin. If you use Istio as your service mesh, you can get started with instrumenting quickly using our integration.

In available languages, you can auto-install OpenTracing to your framework. Configure your tracer and see requests travel through the framework with little to no service-level code required. For other languages, use the API to create a single span by instantiating a tracer and adding instrumentation to a small piece of code and then view that span in Lightstep.

  • C++: Service-level instrumentation
  • C#/.NET: Auto-installer for the .NET framework
  • Golang: Service-level instrumentation
  • Java: Java SpecialAgent installer for many framework libraries
  • JavaScript/Node: Auto-installer for the Node framework
  • Objective-C/Swift: Service-level instrumentation
  • PHP: Service-level instrumentation
  • Python: Auto-installer for many frameworks, data stores, and libraries
  • Ruby: Auto-installer for many libraries

Remember, Lightstep can only display what your system sends it, so instrumentation is key!