Lightstep uses Satellites to collect 100% of the performance data that your tracing instrumentation generates. Satellites collect telemetry data generated by instrumented clients and servers, and then process and temporarily store that data during trace assembly. The Hypothesis Engine (the remote SaaS component) queries the Satellites, records aggregate information about the spans, directs the trace assembly process, and then stores traces durably, all for display in the Lightstep UI.
Learn more about Satellites.
For this Learning Path, you’ll use the Public Satellites, Lightstep’s public pool hosted in the cloud.
Satellites communicate with your instrumentation using an access token. Access tokens are project-specific. You’ll need this access token in the next step when you instrument your service.
Create an Access Token
You create access tokens for projects from the Project Settings page. Access tokens allow the Satellite to report data to a specific Lightstep project.
To create an access token:
Choose the project to create the access token for.
From the Navigation Bar, click Project Settings.
In the Access Tokens table, click Create New.
A new row in the table is created with a token. By default, tokens are not given a name.
It may take up to 5 minutes for the token to propagate to all active Satellites.
To name the token, click Rename, enter a name, and click Rename Token.
Copy the access token, as you’ll need it to add it to your instrumentation as an environment variable.
If you are using the Hipster Shop with this Learning Path, you can now follow these instructions to install it. Copy the access token you just created, as you’ll need to set it as an environment variable during setup.
What Did We Learn?
- Lightstep uses Satellites to collect and process 100% of your telemetry data.
- Project-specific access tokens allow the tracer to communicate with the Satellites.