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

There are pricing implications to migrating to Microsatellites. Please speak with your Customer Success representative before migrating from Classic Satellites.

This document describes steps to take to verify that you’ve installed and configured your Microsatellites correctly.

Verify Microsatellite Log Statuses

  • /var/log/syslog (on Docker and Debian)
  • /var/log/messages (Amazon Linux)

The log should contain output from a self-test:

Satellite Self-Test Results...
Satellite Key authorized for:
1 Organizations [organization name]
5 Projects [project name]
100 Access Tokens [redacted]
Tests: Connected to success
Require unique port numbers: success
Self-Test Status: SUCCESS

If you don’t see a success message, read below to help troubleshoot.

Verify Basic Connectivity

  1. Verify application host to Microsatellite network connectivity. Are you able to ping the Microsatellite from the application host?
  2. Verify that the Microsatellite host is correctly listening. Open a browser and access the Microsatellite’s diagnostic page: http://{satellite_ip}:8000}/diagnostics. The Satellite Diagnostics page should display.

Verify the Microsatellite Can Process Spans

  1. Create a workspace directory under your home directory.

    > mkdir workspace

    Go Setup
    * Ensure that Go 1.7 or higher is installed.
    * Set GOPATH=$HOME/workspace

  2. Setup Lightstep Go Tracer

    > cd workspace
    > go get ''
  3. Run the Span generator

    > cd ~/workspace/src/
    > go run main.go -access_token {access_token} -collector_host {satellite_ip} -collector_port {http_plain_port} -secure=false -operation_name {dummy_operation_name}
  4. Verify that traffic is sent. Go to{project}/live and click Explorer from the left navigation bar. There should now be a value for Operation: {dummy_operation_name}, verifying that the Microsatellite is receiving and sending data.

Possible Service Startup Issues

Check your /var/logs/syslog file on your Microsatellite host for these possible Microsatellite service startup issues:

  • Apr 30 18:18:15 collector-host lightstep-collector[5571]: panic: failed to generate credentials:open /root/certs/mydomain.bundle.pem: permission denied If you are not using a secure connection between the application and the Microsatellite, comment out the tls_cert_prefix: /root/certs/mydomain in your Microsatellite Configuration file. If you are using a secure connection, make sure the certificate file is correct.

  • Apr 30 18:22:12 collector-host lightstep-collector[5729]: panic: listen tcp :80: bind: permission denied By default, the Microsatellite uses port 80 on the Microsatellite host for inbound non-secure communications with the application clients. Because port 80 is a privileged port, you may receive a permission error. You can modify the plain_port: configuration in your Microsatellite Configuration file to use a non-privileged port (above 1024).

Monitor and Tune Microsatellites

Now that you’ve verified that your tracers, Microsatellites, and the Lightstep SaaS are communicating, you need to ensure that the configurations are ideal for the amount of span data that your tracers are collecting from your instrumentation.

Lightstep offers a number of ways to Monitor Lightstep performance. If you see issues, you may need to tune configuration options, add more satellites, or tune your Microsatellite pools and tracers.