This module is a companion to the Performa monitoring system. It is the data collector, which can be installed on all your servers. It collects metrics and sends them to the central Performa server every minute, and is activated by cron. It is shipped as a precompiled binary and thus has no dependencies.
The easiest way to install Performa Satellite is to use one of our precompiled binaries. It can live anywhere on the filesystem, but for these examples we place it into the /opt/performa
directory. Make sure you are root
(superuser) to install this.
mkdir /opt/performa
curl -L https://github.com/jhuckaby/performa-satellite/releases/latest/download/performa-satellite-linux-x64 > /opt/performa/satellite.bin
chmod 755 /opt/performa/satellite.bin
/opt/performa/satellite.bin --install
Note that in this case you will have to select the correct binary for your platform. The static binary flavors available are:
performa-satellite-linux-arm64
performa-satellite-linux-x64
performa-satellite-macos-arm64
performa-satellite-macos-x64
The performa-satellite-linux-x86
binary should work on any 64-bit Linux OS on x86 hardware, including RedHat/CentOS and Debian/Ubuntu. Change x86
to arm64
if you are running Linux on ARM (e.g. Raspberry Pi). If you are installing on macOS, replace linux
with macos
, but note your Mac's architecture (x64
or arm64
a.k.a. Apple Silicon).
Running the binary with the --install
argument will add it to cron, specifically in /etc/cron.d/performa-satellite
, which is set to run once per minute. It also creates a default configuration file, if one doesn't exist.
Performa Satellite expects a JSON formatted configuration file to live in the same directory as the binary executable, and named config.json
. Here is an example file:
{
"enabled": true,
"host": "performa.local:5511",
"secret_key": "CHANGE_ME",
"group": ""
}
Here are descriptions of the properties you can put in the file:
Property Name | Type | Description |
---|---|---|
enabled |
Boolean | This enables or disables Performa Satellite. Set this to false to pause metrics collection. |
host |
String | Set this to the hostname and port of your Performa master server, e.g. performa.mycompany.com:5511 . The default port for Performa is 5511 . |
secret_key |
String | Set this to the same secret key string on your Performa master server. See Secret Key for details. |
group |
String | (Optional) The group ID is optional, and only needed if you have servers with indeterminate hostnames (i.e. serverless, autoscale, etc.). See Groups for details. |
proto |
String | (Optional) If you have configured your Performa master server with HTTPS, Satellite can send metrics securely by setting this property to https: . |
socket_opts |
Object | (Optional) Optionally configure the options passed to the Node.js HTTP library. A potential use case is for SSL self-signed certs (see below). |
max_sleep_ms |
Number | (Optional) Set the maximum random sleep time. Defaults to 5000 ms. See Scalability below for details. |
To connect with HTTPS and allow self-signed certs, add the proto
and socket_opts
properties to your config.json
file:
{
"enabled": true,
"host": "performa.local:5511",
"secret_key": "CHANGE_ME",
"group": "",
"proto": "https:",
"socket_opts": {
"rejectUnauthorized": false
}
}
The Performa Satellite binary executable accepts the following command-line arguments:
Argument | Description |
---|---|
--install |
This runs first-time installation tasks such as creating the cron job and a sample configuration file. |
--uninstall |
This removes the cron job and deletes the config file, if one is found. |
--config |
Optionally specify a custom location on disk for the configuration file. |
--debug |
Setting this flag runs the collector in debug mode, causing it to emit raw stats on the console rather than submitting them to the server. |
--nosleep |
This disables the random sleep that Satellite performs before collecting and sending metrics. |
--hostname |
This allows you to specify a custom local hostname, to use in place of the actual server hostname. |
--fake |
Setting this flag will generate "fake" (semi-random) metrics data. Used for testing purposes. |
--quiet |
This silences all output from Satellite, even fatal errors. |
Performa Satellite is designed to run on many servers, and will randomly delay sending metrics by up to 5 seconds (by default) at the start of each new minute, so not all your servers contact the central master server at the same instant. The same random seed is used for each server (it is based on the hostname) to insure that the metrics collection happens exactly 1 minute apart on each server.
If you have a setup with hundreds of thousands of servers all reporting to the same Performa central server, it is recommended that you increase the max delay from 5 seconds up to 30 seconds. To do this, edit your Performa Satellite config.json
file and add a top-level JSON property named max_sleep_ms
. This value is in milliseconds, so set it to 30000
for 30 seconds.
You can disable the sleep feature by adding the --nosleep
command-line argument.
You can install the Performa Satellite source code by using Git (Node.js is also required):
git clone https://github.com/jhuckaby/performa-satellite.git
cd performa-satellite
npm install
You can then run it in debug mode by issuing this command:
node index.js --debug
To repackage the binary executables for Linux, macOS and Windows, run this command:
npm run package
The MIT License
Copyright (c) 2019 - 2024 Joseph Huckaby.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.