Auditing events
Registered by
Zane Bitter
Currently we only record events about resources, not about API actions.
When a user performs an action, such as creating or updating a stack, we should record events that include, at a minimum:
1) Which action it was
2) The parameters
3) Which user performed the action
Possibly we should also store the template? Maybe that would be a good application for our currently-useless raw_template database table ;)
We might choose to expose these through the existing events API, or more likely extend the API somehow.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Pending Approval
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
It would probably make sense to leverage the CADF work that was done in Ceilometer for this work.
(stevebaker) Is this obsoleted by blueprint send-notification or blueprint user-visible-logs?
(?)
