The fleet: every machine orca is paying for, as Ops' Pools shows the EC2 ones (/ops/pools?kind=ec2, orca.ui.pools) and /api/fleet has them as JSON.
What the page shows comes from three places, none of which reads the
samplers' files when a page is viewed:
orca.instances says which hosts exist, since when, for which run;
orca.fleet_samples holds each live host's last 30 minutes of samples,
one row per sample;
orca.fleet_hourly holds, per hour and role, what the 7-day charts add up
(CPU seconds used and available, bytes in and out), kept 8 days.
The scheduler fills both tables (ingest, every ORCA_FLEET_SECONDS, 30; 0
turns it off). Run instances upload their samples to the run's metrics/
folder (orca.sample) every ORCA_CLUSTER_LOG_SECONDS, so ingest reads
the last lines of each live instance's file from there, a few hundred bytes
of it per instance per pass in effect, and keeps those it hasn't got. The
control instance's sampler (orca sample --out <file> --keep N, started by
the stack's user data) writes a file ORCA_CONTROL_SAMPLES names, and
ORCA_CONTROL_TYPE says what the instance is. Without them the control
instance has no row, unless runs placed on it (orca register --placement control, orca.control) are running, which its row lists; without
ORCA_LOGS no instance has one.
Prices are a small table of us-east-2 on-demand rates for the types orca
runs on: an estimate (Spot hosts cost less, and a stopped-and-started clock
isn't modelled). With ORCA_RUNNER=local no instance is launched, so the
cost tile says "fixed price" instead and shows ORCA_FIXED_COST (free text,
such as €8.49/month; "Fixed" when unset), with no region.