Should contain a temporary storage for alarm detail storage in case back end database is down or in hang stage.
Registered by
Vishal
Ceilometer create alarm api used to create new alarm for certain event and store the details in database. When the database is down or in hang stage on an average of 3 minutes then ceilometer throws error and reject the alarm creation.
For this there should be some temporary storage mechanism or event_storages should always work side by side, so that data is not lost if the database is in wait stage.
Some queuing mechanism can be made so that at least some requests can be stored.
I tested it with ceilometer Kilo release via mongoDB database.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Vishal
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
this needs a spec... or mailing list discussion. what database is hanging? alarm or ceilometer/gnocchi? -- gordc (18.01.16)
(?)