Agent with Docker Compose

The agent repository ships a Compose file that runs the agent together with all three local stores — VictoriaMetrics, Loki, and Tempo — as containers. It is the fastest way to try the agent against a real tenant.

This is a trial, not a deployment

The Compose stack receives OTLP only — it does not collect the host’s metrics, because the bundled configuration has no host-metrics receiver (and on macOS or Windows a container could only see Docker’s Linux VM anyway). For a real install, and to see the machine’s own metrics, use Linux, macOS, Windows, or Kubernetes.

Run it

The Compose file bind-mounts sibling configuration files, so clone the repository first:

git clone https://github.com/LeanSignal/leansignal-agent && cd leansignal-agent

export LEANSIGNAL_ENDPOINT="<tenant>-grpc.eu11.leansignal.io:443"
export LEANSIGNAL_AGENT_KEY="<your-agent-key>"
export LEANSIGNAL_AGENT_NAME="<a-name-for-this-agent>"
export LEANSIGNAL_DATAPLANE_ENDPOINT="https://<tenant>-metrics-ingest.eu11.leansignal.io/api/v1/write"
export LEANSIGNAL_LOKI_ENDPOINT="https://<tenant>-logs-ingest.eu11.leansignal.io"
export LEANSIGNAL_TEMPO_ENDPOINT="https://<tenant>-traces-ingest.eu11.leansignal.io"

docker compose -f deploy/docker/docker-compose.yaml up -d

Three things the Compose trial does differently

It needs explicit endpoints. Every other install derives its endpoints from the tenant name; Compose predates that and still requires LEANSIGNAL_ENDPOINT and LEANSIGNAL_DATAPLANE_ENDPOINT. eu11 is the EU region hosting all tenants today.

LEANSIGNAL_DATAPLANE_ENDPOINT is the full write URL here — ending in /api/v1/write — not the base origin the host installers take. Copying an endpoint between the two doubles or drops that path.

The logs and traces endpoints default to the agent’s own local stores (http://loki:3100, http://tempo:4318). Leave them unset and demanded logs and traces loop back locally and never reach LeanSignal — so export both, as above. Likewise set LEANSIGNAL_AGENT_NAME, or this agent’s telemetry is labeled docker-agent.

Ports

Port	Purpose
4317 / 4318	OTLP in — metrics, logs, traces
3500 / 3600	Loki push in (HTTP / gRPC)
13133	health check

Point your applications’ OTLP exporters at 4317 (gRPC) or 4318 (HTTP).

App in another container?

Inside a container, localhost is that container — not the agent. If the app runs in the same Compose project, join it to the agent’s network and use http://agent:4317. From the host, http://localhost:4317 works.

Manage and investigate

# status
docker compose -f deploy/docker/docker-compose.yaml ps

# logs, per service
docker compose -f deploy/docker/docker-compose.yaml logs -f agent
docker compose -f deploy/docker/docker-compose.yaml logs -f victoriametrics
docker compose -f deploy/docker/docker-compose.yaml logs -f loki
docker compose -f deploy/docker/docker-compose.yaml logs -f tempo

# what is actually being forwarded?
docker compose -f deploy/docker/docker-compose.yaml logs agent | grep 'demand filter' | tail -20

# restart just the collector
docker compose -f deploy/docker/docker-compose.yaml restart agent

# stop, keeping the named volumes (vmdata, lokidata, tempodata)
docker compose -f deploy/docker/docker-compose.yaml down

allowed=0 on a fresh agent is normal and correct — nothing is forwarded until a dashboard or alert demands it. The local stores keep receiving everything either way.

Editing the config from the app

Applying a collector configuration from the LeanSignal app makes the agent exit to restart with the new file. The shipped Compose file carries restart: unless-stopped so the container comes straight back; if you run the image with your own docker run or Compose file, keep a restart policy — without one, an applied config leaves the container stopped.

The local stores are reachable on the host at http://localhost:8428 (metrics), http://localhost:3100 (logs), and http://localhost:3200 (traces) — see Linux for queries that work against any of them.