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    

Use Jaeger Agent with LightStep

If you're currently using Jaeger for tracing, you can configure the Jaeger agent to send that data directly to LightStep Satellites with little change. This is a great way to reuse your existing instrumentation architecture either directly in production or to quickly try out LightStep for the first time.

Use the correct version of Jaeger Agent

You should use version 1.11.0 or later. These versions support secure gRPC.
The minimum acceptable version of the Jaeger agent v1.9.0. This version had experimental support of the gRPC endpoint.

To use the Jaeger agent with LightStep, you need to make the following changes:

  • The LightStep Jaeger adapter only supports a gRPC endpoint for ingesting Jaeger spans. Set this using the following flag:
    --reporter.grpc.host-port=<grpchost:grpcport>
  • If you're using a secure endpoint, configure TLS with the following flag:
    --reporter.grpc.tls=true
  • Satellites need your project's access token to accept the data. The easiest (and recommended) way to do this is to pass the token with the request. You can do this in one of two ways:
    • Launch the Jaeger agent with the flag:
      --jaeger.tags=access_token=<access_token>
    • Set the tag access_token=<access_token> as a part of the configuration when initializing the tracer in the services.

Only have one project?

Then you could launch the satellite in a single project mode and not send a project access token. However, if you add a project, the Jaeger integration will not work.

Using our Public Satellites?

Make sure your tracers use the correct protocol to communicate with the Satellites.

Use Jaeger Agent with LightStep


Suggested Edits are limited on API Reference Pages

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