stado resolver status
Invocation
stado resolver status [OPTIONS]Purpose
Whether this host's resolver is ready, and why not when it is not. Reads the registry and the state the `serve --resolver` role publishes to [`state_path`], so diagnostics remain available when the resolver's own API is down. A non-ready result exits non-zero. Every wait an adapter still stands on is listed under `waiting_opens` with its service, consumer, bind, destination host, endpoint and phase: `open` until the host answers the channel open, `answer` from the client's first byte up the channel until the service's first byte back. One waiting longer than the target's declared refresh interval is a blocker, because its client holds an accepted connection that receives nothing, and every request that would go through that adapter is refused with its sentence until it ends. The live process's `/health` endpoint remains the check for workloads already connected to it.
Required inputs and options
| Input or option | Contract |
|---|---|
--target <TARGET> | Registry target whose resolver to report on. Defaults to the target the published state names, then to this host's identity |
--json | Emit machine-readable output |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.