alarming

Alarms raised by the condition monitoring - listing, updating, open alarm locations.

📄️Returns a page of alarms

Returns one page of the alarm results, filtered and sorted by the server. The alarm table grows without bound - every sweep of the condition monitoring appends to it - so there is deliberately no way to ask for all of it: the size of the answer depends on the requested page size and not on the size of the table.

📄️Update an alarm - a status change, a note, or both

Records a status transition as an entry in the alarm's history. An optional note text can be included on that same entry, and a note-only entry (no status change) is also accepted as long as the new status matches the current one. Returns the stored alarm with its complete history, so a caller does not have to read the alarm back to show what was recorded - the entry it contains is the stored one, with the user of the JWT, the server clock and its id. A call that neither changes the status nor carries a note records nothing and returns the alarm unchanged. Responds 404 if the alarm does not exist.

📄️Where the open alarms sit in the tree

Returns every open alarm with the node it was measured on and that node's ancestors. The explorer builds its per-node indicator from this: the state of a node is the highest criticality and the number of open alarms in its subtree (RG-2), aggregated by the client.