Logical combination of alarm states
A mechanism to combine the states of multiple basic alarms into overarching meta-alarms could be useful in reducing noise from detailed monitoring.
We would need to determine:
* whether the meta-alarm threshold evaluation should be based on notification from basic alarms, or on re-evaluation of the underlying conditions
* what complexity of logical combination we should support (number of basic alarms; &&, ||, !, subset-of, etc.)
* whether an extended concept of simultaneity is required to handle lags in state changes
Blueprint information
- Status:
- Complete
- Approver:
- Julien Danjou
- Priority:
- High
- Drafter:
- Eoghan Glynn
- Direction:
- Approved
- Assignee:
- Mehdi Abaakouk
- Definition:
- Drafting
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Mehdi Abaakouk
- Completed by
- Mehdi Abaakouk
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add combination API
Addressed by: https:/
'and' and 'or' operations for alarms combination
Addressed by: https:/
Use timeutils.utcnow in alarm threshold evaluation
Addressed by: https:/
Move alarm defaults to the API
Addressed by: https:/
Refactor threshold evaluator
Addressed by: https:/
Don't allow to set alarm on not owned resource
Addressed by: https:/
Allow to change only the alarm state
Addressed by: https:/
Fix the developer documentation of the alarm API
Addressed by: https:/
Convert BoundedInt value from json into int
Addressed by: https:/
Handle manually mandatory field
Work Items
Dependency tree
* Blueprints in grey have been implemented.
