What Status shows
Status reports the latest recorded probes for configured platform surfaces. The public page and JSON response show monitored hosts, last check times, HTTP results, latency when available, and consecutive-failure health. This is recorded evidence rather than a new check performed when you open the page.
Read health
Use Get Status probe health for a worked request and response, or browse the Status action reference. The public result can be cached for 15 seconds. An empty services array means no recorded probes; it does not prove all applications are available.
A host is healthy with zero consecutive failures, degraded with one or two, unhealthy with three through eleven and dead with twelve or more. Inspect both the last HTTP result and the health classification; a successful request for the page alone does not establish a healthy application.
Monitoring and operator workflows
Monitoring runs probe requests on the configured schedule. Authorized operators can request an immediate poll, inspect the dashboard contribution, and manage incident and maintenance records through permission-scoped actions. Status is platform tooling and has no tenant or app-local workspace database.
Incident and maintenance records are separate from the current public probe JSON and HTML page. Their authenticated list/get actions support ID discovery and read-back. Updating an incident replaces its current message and increments revision; it does not append a public timeline. Creating or transitioning a lifecycle row can enqueue a notification. Delivery depends on configured notification infrastructure and must be verified separately.
Scope and limits
The documented local examples use real route handlers and migration-created SQLite tables with synthetic identity, clock and remote probe dependencies. They do not certify live provider availability, deployment or notification delivery. No live incident, maintenance window or permission was changed while producing these examples.