Expand description
rusty_time-api — typed reports and ops.
Everything a human sees through rtimec or rtimed --json is one of these
types serialized as JSON: the CLI is a thin consumer, and a test or an agent
is the same consumer with a different transport (mission plan §5). Internal
wire moves to oxicode at M4; the public shape stays JSON.
Structs§
- Client
Row - One row of the MRU client log (
debug.clients). - NtsReport
- What NTS did during a query (
status.ntsdata’s client half). - Query
Report - The result of a one-shot
rtimed query. - Sample
Report - One measured exchange, as reported by
rtimed query. - Server
Stats Report - Server counters (
status.serverstats) — the chronycserverstatsanalog. - Tracking
Report - Daemon tracking state (the
status.trackingop).
Enums§
- Control
Endpoint - Where the control plane actually listens, resolved from what the operator typed.
- Control
Request - A request on the control socket. One variant per op (mission plan §5): the CLI, a test and an agent are all just clients of these.
- Control
Response - The answer to a
ControlRequest.
Functions§
- control_
endpoint - Resolve a
--controlargument for this platform. - default_
control_ spec - The default control name.