'Locked' alarms

Registered by Witek Bedyk on 2016-06-20

The operator would like to be able to define an alarm which after transition to ALARM state, stay in that state until it is manually reset. The new alarm definition attribute 'locked' should be introduced.

Blueprint information

Status:
Started
Approver:
Roland Hochmuth
Priority:
High
Drafter:
Witek Bedyk
Direction:
Needs approval
Assignee:
Witek Bedyk
Definition:
Pending Approval
Series goal:
Accepted for trunk
Implementation:
Started
Milestone target:
None
Started by
Roland Hochmuth on 2016-07-16

Related branches

Sprints

Whiteboard

monasca-common
---------------------------

  * add property 'acknowledgeable' to AlarmDefinition data model

monasca-api
-------------------

* update data model
* send the descriptive reason with PATCH /v2.0/alarms/{alarm_id} request to reset the alarm state
* extend POST, PUT, PATCH /v2.0/alarm-definitions

monasca-thresh
------------------------

* extend the logic to 'lock' the alarm, state transition ALARM -> OK or ALARM -> UNDETERMINED should be possible only via API

monasca-ui
------------------

* add the possibility to define, update 'locked' alarms
* display the new property
* add the possibility to reset the alarm with PATCH command

openstack/python-monascaclient
--------------------------------------------------

* add the possibility to define, update 'locked' alarms
* display the new property
* add the possibility to reset the alarm with PATCH command

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.