Data in: telemetry, pass logs and files
Data reaches Constellation five ways. Pick by what you have: link telemetry from your ground stations, a log of the passes you flew, or files in any other format. Every way checks its IDs against your network config, so set that up first.
| Way in | Use it for | Tagged | Reference |
|---|---|---|---|
| The fleet agent | Applications on your Linux hosts publish to a local socket; the agent buffers to disk and delivers, so they never hold the API key | Live | Fleet agent |
POST /telemetry | A backend or script sends records in batches of up to 1,000 | Live, unless a record says otherwise | Telemetry |
gRPC TelemetryIngest.Write | A high-rate producer, with a live key that has telemetry:write | Live | gRPC ingest |
POST /telemetry/pass-logs | A CSV of flown passes, for an audit | Audit | Pass logs |
PUT /telemetry/files/{source}/{name} | Anything else, in any format, stored as it is; large files over SFTP | Not telemetry | Telemetry files |
Live, audit and sim
Every telemetry record belongs to one dataset, named by its dataset field:
dataset | Means | Written by |
|---|---|---|
live, or none | Measured on your fleet as it flies | The fleet agent, gRPC, and POST /telemetry by default |
audit | A backfill of passes already flown, for an audit | POST /telemetry/pass-logs, or a record that says so |
sim | Simulated, not measured | A record that says so |
The dataset is part of a record's identity, so an audit backfill or a simulation never overwrites or mixes into your live series. An audit run reads only the dataset it names ("dataset": "audit" on POST /predictions). The Platform labels every view by what it shows: Live, Audit, Sim, Scenario or Demo fleet. The demo fleet's simulated telemetry names only the demo's own satellites and antennas, and Integrations never counts it as yours. See Data modes and datasets.
What the API checks
- Every ID must be in your latest network config: the ground station, its antenna, the satellite, and the radio when a record names one.
- Every field must be on a fixed list with its type. A field the list does not hold is dropped from its record; the rest of the record is written.
POST /telemetrywrites every record that passes and lists the rest by index inrejected_indices, each problem inrejections. It refuses the whole batch,400 invalid_input, only when no record passes.- A pass log is all or nothing: one bad row writes none, and the answer lists every problem by row.
Sending a record again rewrites the same point, and a pass log uploaded again counts each contact once. See Idempotency.
Pass logs for audits
A pass log is one row per pass flown: satellite_id, antenna_id, aos_utc, los_utc, bytes_delivered and status (ok, failed or missed). Each row becomes an audit record at the pass's AOS. An audit-ledger run then sets each computed pass against the contacts it overlaps. In the Platform, Past on Passes, with Audit chosen, takes the upload and runs the audit; see Free audit.
Files
A telemetry file is stored unchanged under a source label you choose, and each upload is a new file. Files are not telemetry records: they do not appear in GET /topology or reach a forecast by themselves.
See what arrived
GET /topologyreturns the newest value of each field per link, and series reads return records over a window.- Verify delivery checks the fleet agent end to end.
- In the Platform, a row on Fleet shows a gray dot when its ground station or satellite has sent no telemetry in the last five minutes, and Integrations, Data in, shows how many links the fleet agent reports and its newest record.
Live link telemetry is what the models read. Link SNR is trained on link telemetry and learns each antenna from the live records you send: send one record per link at least once a minute while it is in view, with es_n0_db, elevation_deg and range_m. On Operator and above, calibration fits the SSA pass forecast and RF interference models to your own telemetry each night; Explore uses the same models without it.
Next: Install the fleet agent.