Adding Alarm Conditions

Registered by Craig Bryant on 2015-03-12

There are already many good ticket handling systems and it does not make sense to add this functionality to Monasca. However, there is a desire to allow other developers using Monasca to add simple ticketing. To that end, we propose adding the following to Monasca Alarms:

1. A Condition Field with the possible values of: INITIAL, OPEN, ASSIGNED and RESOLVED
2. A User field of size 255 characters. The contents of this field are the responsibility of whoever sets it, monasca will not try to set it based on Keystone User
3. A Comment field of size 16384 characters

An Alarm will be created with the condition of INITIAL and state of UNDETERMINED. If it changes state to ALARM, condition will go to OPEN. If the first state transition is to OK, condition will remain at INITIAL.

When an Alarm changes state to ALARM, condition will be set to OPEN if condition is INITIAL or RESOLVED. Otherwise, the condition will not be changed by any state transition.

The Condition is store on the Alarm and not on the Alarm History. At ticket would be created when the condition changes to OPEN. This means that when an Alarm goes to the ALARM state, then OK, and then back to ALARM, it will still be considered the same ticket. unless the condition was

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Craig Bryant
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.