This topic is about our Classic Satellites. If you installed Satellites after 4/06/2021, you are probably running Microsatellites.

Lightstep offers a public shared Satellite pool for lower throughput production environments or development environments. Not having to install and maintain an On-premise Satellite pool speeds up the initial production of meaningful traces right away. As your traffic increases, consider running On-premise Satellites, as they can be tuned to suit your application’s higher traffic load.

Note the following:

Encrypted connections with TLS

Lightstep uses TLS certificates signed by the certificate authority Let’s Encrypt. To establish a secure (TLS) connection to Lightstep’s public Satellite pool, any machine that runs a tracer must have a root certificate installed. Most operating systems come with one of both certificate(s) pre-installed. If not, you can add them manually by downloading one from here.

Connecting to Lightstep Public Satellite pool

In general, Lightstep OpenTelemetry Launchers and OpenTracing tracer clients are pre-configured to connect to the public Satellite pool by default, with no custom settings.

If needed, please refer to each language-specific tracer client for information about the configuration options it supports. You can customize these, using the following protocols. All use secure TLS (ingest.lightstep.com:443) endpoints.

Protocol Format
HTTP JSON
HTTP Thrift
HTTP Proto
gRPC Proto