Reference/Agent reference

Agent reference

The accelerated binary — commands, configuration, profiles and what it sends.

accelerated is the AccelerUp origin agent. Current version 0.11.0.

Commands

text

accelerated login --server https://monitoring.qrdev.org   Authenticate this server
accelerated install                                       Install + start the systemd service
accelerated run                                           Run in the foreground
accelerated status                                        Show local config + service state
accelerated uninstall                                     Stop + remove the systemd service
accelerated version

accelerated login -h lists the login flags.

Transport

The agent dials out over a websocket to /api/v1/agent/connect and authenticates with an enrolment token. Nothing needs to be open inbound, and the agent never listens on a port for the control plane.

If the websocket cannot be established, /api/v1/agent/ws-check is a public, inert diagnostic: it upgrades, reports whether the upgrade survived the proxy chain, and closes. A failed handshake is otherwise invisible from both ends.

Profiles

The profile is set on the machine and caps what the control plane may ask. It cannot be widened remotely.

Profile	Allows
`observe`	Reporting only: vitals, probes, collectors, logs. No shell, no file transfer, no commands, no failover
`operate`	The above, plus declared commands and unit actions. No interactive shell, no file transfer
`full`	Everything, including the interactive terminal and file transfer

Set with ACC_PROFILE. The profile is logged at every start, not only when it blocks something — an operator who installed with observe and later wonders why the terminal button does nothing finds the answer in the first ten lines of the journal.

Configuration

Variable	Purpose
`ACC_PROFILE`	`observe` / `operate` / `full`
`ACC_SERVER_URL`	Control-plane URL
`ACC_SECRETS_FILE`	Local credentials for collectors. Redacted unconditionally in everything the agent sends
`ACC_CHECK_INTERVAL`	Seconds between health checks
`ACC_FAIL_THRESHOLD`	Consecutive failures before acting
`ACC_ALLOW_RAW`	Whether guarded raw commands are permitted

Blue/green applications are configured per app with a blue port, a green port and an upstream file. An agent with no blue/green apps is a normal, supported configuration — a database box, a worker, a build host — and still reports vitals, ships logs, runs probes and executes commands.

What it reports


Host vitals	CPU, memory, disk, load, uptime, clock drift
Listeners	Which ports are open and what is behind them
Processes	What is running
Health documents	The application's own view of its dependencies
Probes	Reachability from this server
Collectors	Exporter scrapes, log watches, config drift
Units	systemd unit state

Health documents travel whole, not as a count of failures. A check added on the application side must appear in AccelerUp with no change on the agent side — that is the entire reason for reading a document rather than writing a collector per dependency — and a count cannot carry a name.

Secrets

Credentials for collectors live in a local secrets file. They are redacted unconditionally in everything the agent sends, including in error messages and in the terminal transcript.

Dead-man's switch

An agent that stops reporting raises an alert. "Has stopped reporting" and "is unreachable" are distinct alerts with different causes and different fixes, and they are never collapsed into one.