alarming in piplines
Registered by
gordon chung
currently alarms are pretty heavyweight in ceilometer (recorded in backend, need their own services running). it would be cleaner/leaner to have them defined as part of pipeline but can it cover all the uses cases of alarming?
this bp is to disucss this
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- gordon chung
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- gordon chung
Related branches
Related bugs
Sprints
Whiteboard
what's the use case for alarm history? can this be covered by alarms in pipeline?
just adding some thoughts here. but if history is required to be stored, we can send notifications and store the events in Celiometer as well.
--gordc 18/03/14
(?)
