List a system's members' alarms
const url = 'https://example.com/api/v1/systems/example/alarms';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/systems/example/alarmsEvery member’s alarms in one read, newest first, each naming its component: the active ones whatever their age, and those cleared in the last 30 days, capped at 500. It is what a system’s Activity reads to explain its incidents, one request however many members the system has. Gated by system:read; an out-of-scope system is a non-disclosing 404.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The system’s name, or a dotted address (e.g. boi.17c.$sys.av)
The system’s name, or a dotted address (e.g. boi.17c.$sys.av)
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
object
A URL to the JSON Schema for this object.
Whether anybody has recorded seeing this alarm; says nothing about whether it is still raised
When a human first recorded seeing this alarm; null while nobody has. Independent of cleared_at
Who acknowledged it, by name; empty while unacknowledged, or once that principal has been purged (the audit log keeps the name)
Null while the alarm is active
The component the alarm is on, by name
The component’s uuid, the stable form of component
The condition identity: one open alarm per (component, dedup_key)
The event rule that raised the alarm, by name; absent when an operator raised it
The raising rule’s uuid
The severity level the alarm was raised at, by name (see /severity-levels)
Example
{ "$schema": "/api/v1/schemas/SystemAlarmsOutputBody.json", "alarms": [ { "$schema": "/api/v1/schemas/AlarmBody.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"}