Manage agents

Agents are the edge collectors that stream filtered telemetry to LeanSignal — one per cluster or environment. The Agents page in the LeanSignal app is where you register them, watch their connection state, and see how much of the available telemetry each one actually stores.

Register an agent

1. Go to Agents → Add Agent (editor or admin role) and give it a name — 3–64 characters, letters, numbers, underscores and hyphens (for example production-collector-01).
2. Open the new agent (click its name) and copy the Agent Key — visible to admins only, masked until you reveal it, with a copy button.
3. Deploy the agent with that key — see Install the agent, or the guide for your platform: Linux · macOS · Windows · Kubernetes. Within seconds of dialing in, the agent shows Connected.

Connection status

The Status column (and badge in the detail view) shows:

Status	Meaning
Connected	The control stream is up.
Healthy	Connected and reporting normally.
Disconnected	The agent has dropped its control stream — see Troubleshooting.
Unknown	No status reported yet.

One thing to know about the transport: an agent key supports one connection at a time. If a second agent dials in with the same key, it is rejected until the first stream ends — so give every agent its own key rather than sharing one.

Reading the telemetry numbers

The Ingesting timeseries column shows stored/available (pct%) — for example 21/209,747 (0%):

• Available is everything the agent sees: the full index of timeseries in its local, full-fidelity store.
• Stored is what the current demand set actually forwards to your central dataplane.

This ratio is demand-driven observability in one number — the gap between the two is telemetry you’re not paying to keep centrally, but can start collecting the moment you demand it. 0/N means no demand covers this agent’s metrics yet; import an integration or build a dashboard and watch it move.

The agent detail view adds Available Timeseries, Stored Timeseries, and Demand Last Update (when this agent last received a demand-set push), plus connection timestamps.

Agent keys

The agent key authenticates the agent to your tenant — treat it like a secret:

• Only admins can reveal or copy keys; editors and viewers see them masked.
• Inject it via an environment variable, secret manager, or Kubernetes Secret — never commit it (see Agent configuration).
• Deleting an agent invalidates its key and stops its telemetry — the delete dialog warns you before confirming.

Next steps

• The agent — install, configure, and operate it on Linux, macOS, Windows, or Kubernetes.
• Work with demands — decide what agents forward.
• Troubleshooting — an agent that won’t connect.