How-to guide

Install Signals

Get the Signals daemon and the signalsctl CLI onto your host or cluster. Pick the install path that fits your environment — the Docker image is the quickest way to get a daemon running, release binaries suit host installs, and Helm is for Kubernetes.

Signals monitors PostgreSQL 14 or newer. Choose one of the options below, then verify the install before moving on to configuration.

Docker

The image bundles both binaries and runs the daemon as its entrypoint. Mount your config at /etc/signals/signals.yaml and a volume for the snapshot store at /data.

docker run -d --name signals \
  -v "$PWD/signals.yaml:/etc/signals/signals.yaml:ro" \
  -v signals-data:/data \
  -p 127.0.0.1:8081:8081 \
  ghcr.io/elevarq/signals:<version>

Replace <version> with a tag from the releases page — pin a specific release (e.g. v1.2.0) for production; ghcr.io/elevarq/signals:latest is fine for a quick trial. For the published port to be reachable, the mounted config must bind the API on 0.0.0.0:8081 ( the -p 127.0.0.1:8081:8081 mapping keeps it on host loopback) — see the tutorial and configuration reference.

Pre-built binaries

Each GitHub release publishes signals-<os>-<arch> and signalsctl-<os>-<arch> for linux/darwin × amd64/arm64. Substitute the latest version and your platform:

base="https://github.com/Elevarq/Signals/releases/download/<version>"
curl -fsSL -o signals     "$base/signals-linux-amd64"
curl -fsSL -o signalsctl  "$base/signalsctl-linux-amd64"
chmod +x signals signalsctl
sudo mv signals signalsctl /usr/local/bin/

Build from source

Building from source needs Go 1.26 or newer.

git clone https://github.com/Elevarq/Signals.git
cd Signals
make build          # produces bin/signals and bin/signalsctl

Kubernetes (Helm)

Install the chart from the OCI registry, pointing at your own values.yaml:

helm install signals oci://ghcr.io/elevarq/charts/signals \
  --version <version> -f values.yaml

Verify

Confirm the CLI is on your path and reports a version:

signalsctl version

Next, grant Signals the read-only database access it needs and configure how it connects: Create the monitoring role and Configure authentication.