Read a location's health
const url = 'https://example.com/api/v1/locations/example/health';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/locations/example/healthThe location’s current verdict, worst-wins over every system placed anywhere beneath it, with those systems and their verdicts as the drill-down (the system health read names the role, the capability, and the alarm). Transitions are the recorded edges over the last 30 days. Gated by location:read; an out-of-scope location is a non-disclosing 404.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The location’s unique name
The location’s unique name
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
The contributing roles; empty for a location
object
The active alarms that degraded them
object
The required capabilities an active alarm has taken away; empty when the role is merely short-staffed
What an impaired role means for its system: outage, degraded, or none
True when satisfying is below quorum
The capabilities a component must ALL provide to fill this role
How many assigned components can currently fill the role
The systems beneath a location with their verdicts; empty for a system
object
The recorded edges over the window, oldest first: one entry per change, never a sample
object
Healthy, degraded, or outage: the rollup of the roles or systems served beside it
Example
{ "$schema": "/api/v1/schemas/EstateHealthOutputBody.json"}default
Section titled “default ”Error
object
A URL to the JSON Schema for this object.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
Example
{ "$schema": "/api/v1/schemas/ErrorModel.json", "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}