LightStep

LightStep Documentation

Welcome to the LightStep developer hub. You'll find comprehensive guides and documentation to help you start working with LightStep as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Already Instrumented?

If you've already instrumented your system, but were using another tracing library, no worries! LightStep can ingest that instrumentation with almost no additional code needed.

LightStep can ingest the following instrumentation:

  • Jaeger Agent and Zipkin: If you've been using Jaeger or Zipkin as your distributed tracing monitor, switching to LightStep is easy! LightStep's Satellites can injest data from both with very little change required.
  • Datadog: If you've been using Datadog as your APM, you can send data from their tracers to Lightstep.
  • OpenCensus: Export data from your OpenCensus instrumentation into LightStep.

Using Tracers from Different Vendors

If you are using different tracers for different parts of your application, for example, Zipkin for your client and LightStep for your server, no problem! In many cases, LightStep can still ingest the data and create traces.

Datadog and LightStep

If you're using a mix of Datadog and LightStep you must use B3 header propagation.

Limitations:

  • Datadog's Python tracer does not support B3 header propagation.
  • LightStep only supports B3 header propagation for its Java and C# tracers

Zipkin and LightStep

If you're using a mix of Zipkin and LightStep you must use B3 header propagation.

Limitations:

  • LightStep only supports B3 header propagation for its Java and C# tracers

Jaeger and LightStep

If you're using a mix of Jaeger and LightStep you must use Zipkin's B3 header propagation.

Limitations:

  • Jaeger's C++ tracer does not support B3 header propagation.
  • LightStep only supports B3 header propagation for its Java and C# tracers

Already Instrumented?


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.