Fleet telemetry
Fleet telemetry is off on every installation. With it off, Prism builds no exporter and sends no telemetry of any kind. It is meant for an installation that takes part in a measurement program run by a receiver operator you trust; most installations never turn it on.
Nothing can turn it on remotely. It is on only when config.toml says so.
What leaves when it is on
Section titled “What leaves when it is on”Three fixed classes, built from allowlists, with identifiers replaced by pseudonyms (an HMAC with a per-instance key that never leaves the machine):
- outcome events (worked or not, with closed reason codes);
- orchestration trace metadata (which models were tried, in what order, with what result, cost and latency);
- a sanitized projection of the status snapshot.
What never leaves
Section titled “What never leaves”Prompts, responses, tool arguments and generated text; credentials and the fleet token; configuration values; raw session or request identifiers; free-text error messages; URLs, file paths and machine identity.
Turn it on
Section titled “Turn it on”The installer asks for consent and shows the notice; it enables the export
only after you type yes. In non-interactive mode it needs
--fleet-consent-yes together with the receiver URL and token, and never
enables it otherwise. The acceptance is recorded in the consent/ directory
next to the configuration.
By hand:
[fleet]enabled = truereceiver_url = "https://fleet.example.com" # https requiredtoken_env = "PRISM_FLEET_TOKEN" # environment variable with the instance token# push_interval = "2m" # default 120 secondsPut the token in the environment of Prism’s service (for example
~/.config/prism/prism.env), never in config.toml. If the variable is
empty, Prism logs a warning, disables only the export and keeps routing.
Run from a terminal, prism config check says the variable is not set in
that shell (the service may set it) and still passes; Versions → Check
configuration in the console checks inside the service, with its own
environment.
A slow or unreachable receiver does not slow down requests: the export resumes from its saved position later, and the receiver removes duplicates.
Turn it off
Section titled “Turn it off”Set enabled = false in [fleet] (or remove the section) and restart
Prism. Prism works the same without it. Turning it off stops new exports; it
does not delete what the receiver already holds.