Take an alarm out of the archive
PUT/alarming/unarchive
Removes the archive marker with its time, user, reason and period, whoever archived the alarm and whenever - an administrator's decision, which is why it needs a comment. What the marker said is not lost: the archiving stays in the alarm's history, and this call adds an entry of its own (archiveAction UNARCHIVED, the comment as its content). Nothing else resets the flag: neither a status change nor anything the condition monitoring does to the alarm touches it, and the automatic archiving leaves an alarm alone once it has been taken out of the archive. An alarm that is not archived is left as it is and returned without a new entry. Returns the stored alarm. Responds 400 if the comment is missing or blank, 404 if the alarm does not exist.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- default
OK
the default error response
Unauthorized — the bearer token is missing, expired or invalid, or carries no role. Errors raised by the security aspects contain an ErrorDto body; requests rejected by the security filter chain may have an empty body.
Forbidden — the authenticated user lacks the required role or access rights.
Entity not found.
the default error response