Status page
This page describes what a status page for a dynamo-core deployment can show, using only the core's own monitoring: its Prometheus metrics, the alert rules in deploy/observability/alerts.yml, and the GET /healthz probe. It shows the state of each component now and in the past. It makes no promise of uptime or response time; the targets behind the states are on service levels and limits, and they are design targets, not commitments.
Components
| Component | What it covers |
|---|---|
| Core API | Whether the deployment answers at all: the owner API, the plugin wire and, on a multi-tenant deployment, the front door |
| Admission | Opening streams, metering and reserving: how fast those requests are answered, and whether they are answered without a server error |
| Scheduler | The background work that signs vouchers, takes checkpoints, finalises settlements, renews credit card holds, expires approvals and freezes, and delivers webhooks |
| Settlement | How long signed work waits for a checkpoint, shown per funding mode the deployment runs (Control Mode, stablecoin escrow, credit card rail) |
| Adopted-rail claims | Claims of payees' vouchers on an adopted payment rail; shown only on a deployment that has one |
States
| State | What it means for a user |
|---|---|
| Operational | The component is within its targets |
| Degraded | The component works, but slower or later than its target. Requests are still answered, and signed work is still settled, just later |
| Outage | The component does not work. Requests may fail, or background work has stopped |
| Paused by the operator | The operator paused the deployment with the main switch. New work is refused on purpose, and work that was already signed stays settleable. This is not a fault |
A component is never shown as better than its worst current alert.
How each state is derived
Each state comes from an alert rule in deploy/observability/alerts.yml, so the status page and the on-call alerts never disagree.
| Component | Operational | Degraded | Outage |
|---|---|---|---|
| Core API | /healthz and the scrape answer | not used | DynamoCoreDown: the scrape fails for 2 minutes |
| Admission | p95 admission latency at most 250 ms and server errors at most one request in a thousand | DynamoAdmissionLatencyHigh: p95 above 250 ms for 10 minutes | DynamoAvailabilityLow: more than one request in a thousand answers 5xx for 10 minutes |
| Scheduler | a scheduler holds the lease and no duty is overdue | DynamoDutyBacklog or DynamoDutyFailing | DynamoSchedulerLeaseLost or DynamoSchedulerNotRunning |
| Settlement (lag shown per mode) | lag at most 15 minutes | DynamoSettlementLagHigh: the largest lag over every mode above 15 minutes for 10 minutes (one alert; the per-mode lag shows which mode) | not derived from metrics; the operator posts it |
| Adopted-rail claims | no failed or lost claim | not used | DynamoRailClaimFailed: a claim failed or was lost in the last 30 minutes |
"Paused by the operator" is not in the metrics. The main switch's state is read with the owner token at GET /owner/v1/main-switch, so the operator posts it by hand.
What the page never shows
- Metric values with their labels. Route patterns, reason codes and duty names are operator data; the page shows component states only.
- Anything about one tenant, budget, stream or payee. The core's metrics carry no such label, so a multi-tenant deployment's page shows deployment-wide states only.
- An uptime percentage or any figure that reads as a promise.
Notes for operators
GET /healthzneeds no credential and answers only the service name and the owner-api version, so an external prober can use it. Only the hosted entry and the multi-tenant router serve it.- Scrape
GET /metricsfrom inside your network withCORE_METRICS_TOKEN; never expose that token to the status page itself. - On a multi-tenant deployment the scheduler lease metric reads 0 even while tenant duties run (see known limits). Derive the Scheduler component there from the duty-run counters (
dynamo_scheduler_duty_runs_total) instead of the lease alerts. - Running the scheduler, backups and alerts is covered in run your instance.