pub fn admin_router() -> Router<Arc<AppState>>Expand description
Build the router served on admin_server_port.
Liveness and readiness only. The point of a separate port is that it can be reachable from an orchestrator without the API being reachable from the same place, so nothing that reads or writes data belongs here.
/live and /ready are the names PostgREST’s admin server uses; /health
is the same answer as /live under the name the main API already serves.
With the otel feature, /metrics too: the server’s metrics as
Prometheus text. Here and never on the API’s port, for the same reason as
the rest – what the pool and the token cache are doing is the operator’s
business, not every client’s.