List alarm events
Lists the alarm lifecycle events in a project as a flat feed. Rows are sorted by synced_at, oldest first. You can filter by site. To read incrementally, use the updated_since, after, and after_event_id watermark. All IDs are DUET IDs.
BearerAuthorizationBearer <token>project_id*stringThe ID of the project to read alarm events from.
site?stringReturns only events from this site.
updated_since?stringThe replay watermark. Returns events that DUET stored at or after this time, compared against synced_at. Rows are sorted by synced_at, oldest first. To resume, set updated_since to the last row's synced_at, after to its duet_occurrence_ref, and after_event_id to its event_id.
date-timeafter?stringThe duet_occurrence_ref of the last event you received. Requires updated_since and after_event_id.
after_event_id?stringThe event_id of the last event you received. Requires updated_since and after.
limit?integerThe maximum number of rows to return. The default is 10,000 and the maximum is 100,000. A page with fewer than limit rows is the last page.
1 <= value <= 10000010000offset?|The number of rows to skip. For replay, use the updated_since and after watermark instead. An offset can skip or repeat rows when rows change between pages.
0 <= value0The alarm events, oldest synced_at first.
application/json- response
[index: integer]?curl -X GET 'https://api.enurgen.com/platform/v1/alarms/events?project_id=string'[ { "event_id": "string", "occurrence_id": "string", "duet_occurrence_ref": "string", "type": "raised", "kind": "string", "created_at": "2019-08-24T14:15:22Z", "synced_at": "2019-08-24T14:15:22Z", "body": "string", "user_id": "string", "user_email": "string", "external_user_id": "string", "detail": null }]Get an alarm occurrence GET
Returns one alarm occurrence with its full lifecycle timeline, oldest event first. Returns `404` if the project has no occurrence with this ID. All IDs are DUET IDs.
List alarm occurrences GET
Lists the alarm occurrences in a project, each with its newest lifecycle events. Rows are sorted by `synced_at`, oldest first. You can filter by status, severity, and site. To read incrementally, use the `updated_since` and `after` watermark. All IDs are DUET IDs.