If you’ve already instrumented with OpenTelemetry using Collectors, then getting data into Lightstep requires only an edit to the YAML config file. You need to configure the Collector to use OTLP to send data to the Lightstep Satellites using your project’s access token.

In the collector-config.yaml file, add an otlp exporter that points to your Satellite. The configuration depends on which type of Satellite you’re using.

If you are running in single project mode, you can omit the access token.

Start tabs

On-Premise Satellites

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
exporters:
    prometheus:
        endpoint: "0.0.0.0:8889"

    logging:
        loglevel: debug

    # Configure collector to send data to on-premise satellites.
    otlp:
      endpoint: <YOUR_LOAD_BALANCER_DNS_NAME_OR_IP_ADDRESS>
      insecure: true
      headers: {"lightstep-access-token":"<YOUR_ACCESS_TOKEN>"}
    
    . . .

Public Satellites

1
2
3
4
5
6
7
8
9
10
11
12
13
exporters:
    prometheus:
        endpoint: "0.0.0.0:8889"

    logging:
        loglevel: debug

    # configuring otlp to public satellites
    otlp:
      endpoint: ingest.lightstep.com:443
      headers: {"lightstep-access-token":"<YOUR_ACCESS_TOKEN>"}

    . . .

Developer Mode

1
2
3
4
5
6
7
8
9
10
11
12
exporters:
    prometheus:
        endpoint: "0.0.0.0:8889"

    logging:
        loglevel: debug

    # configuring otlp to developer satellites
    otlp:
      endpoint: localhost:8360

    . . .

End code tabs

You can find a full example of a collector-config.yaml here.