Read an alarm's timeline
const url = 'https://example.com/api/v1/components/example/alarms/example:timeline';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/components/example/alarms/example:timelineThe alarm’s history in one list, oldest first: the events that carry it (an event rule’s fire event, which opened it, and its clear event, which resolved it) merged by time with its audit rows (the raise, each acknowledgement, the clear, and a rule edit that opened or resolved it, naming the editor). At one instant an event comes before the audit row it caused. Gated by alarm:read; a component outside the caller’s component read scope, and an alarm not on the component, are a non-disclosing 404.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The component’s name, or a dotted address (e.g. boi.17c.415a.$comp.display-1)
The component’s name, or a dotted address (e.g. boi.17c.415a.$comp.display-1)
The alarm id
The alarm id
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
Oldest first; at one instant an event comes before the audit row it caused
object
Who acted, by name; absent when the platform acted for a rule
When it happened
The series instance (an endpoint) an event is about
An event carrying the alarm (a rule’s fire or clear event), or an audit row about it
The event’s message, or the message the alarm was raised with
The event rule the entry belongs to, by name: the rule that wrote the event, or the rule the platform acted for
The event’s type (e.g. condition-started), or the audit action: raise, acknowledge or clear
Example
{ "$schema": "/api/v1/schemas/AlarmTimelineOutputBody.json", "entries": [ { "kind": "event" } ]}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"}