Support Oslo.rpc.notifications for major operations
Heat should emit notifications in the following situations:
1. For each CrUD operation. Anything that mutates the state of the system.
2. Retrieval operations, the R in CRUD, are optional and likely too chatty, but if the retrieval is something the client is billed for, an event should be emitted. This is usually done as an end-of-day operation under a specific “---.usage” event.
3. Exceptions and error conditions in the system should be emitted on the ERROR queue.
4. Around any operation that is complex, multi-staged or could take a long time to perform, separate .start and .end notifications should be emitted. This can help with performance tuning and stall detection.
These notifications can be consumed by downstream systems such as Ceilometer and StackTach for monitoring and billing support.
(more details about notifications are available here: http://
https:/
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Randall Burt
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Randall Burt
Related branches
Related bugs
Sprints
Whiteboard
(scroiset) seems to be addressed here too : https:/
This has already been implemented by blueprint send-notification
