This topic is about Microsatellites. If you installed Satellites previous to 4/06/2021, you are probably running legacy Satellites.
Microsatellites are straightforward to deploy using a Docker image (with or without a Helm chart), AWS/AMI, or a Debian package. Installation and configuration differ depending on the environment you’re installing to, but you’ll need the following information for all installation types.
As part of your Microsatellite configuration, you’ll need a Satellite key. Lightstep uses this key to authenticate and communicate with the platform. Satellite keys expire after 1 year for security purposes. You’re notified by email when the key is about to expire. See Generate Satellite Keys for instructions for generating and renewing keys.
Only users with the Admin role can generate Satellite keys.
CPU and Memory Recommendations
Microsatellites don’t have strict CPU and memory requirements. One recommendation is to start with 2 CPU and 2 GB machines and see how much memory and CPU is utilized. We expect a 2 CPU and 2 GB machine to support 6 MB/s based on internal benchmarking.
Microsatellites have a max throughput. You should monitor the
forward_spans.dropped to make sure you haven’t reached that point. Learn more about monitoring and tuning your Microsatellites here.
Given the above recommendations, it is possible to allocate multiple Microsatellite instances to the same virtual machine or physical hardware. Remember to ensure you have enough CPU, memory, and network I/O for all the Microsatellites when stacking them.
Whitelist to Allow Outbound Traffic
You must allow outbound traffic from the Microsatellites by whitelisting the following IP addresses, on TCP ports