Audit parameters should be persistent in Db
When you start an audit, an new Audit object is created into Db with a reference to an Audit Template object. When processing an audit request, parameters taken into account by the Watcher DE come from Audit object itself and also from Audit Template ones (goal name, ...).
Problems:
If we update the Audit Template parameters or if we remove the Audit Template, we lose important information about the Audit itself. What would be the consequence for a periodic audit ? What about data integrity for soft-deleted audit objects (useful for history) ?
If we introduce parameters for goals (as thresholds, ...) , we should be able to update them. So how to keep persistent data for all audits done to satisfy such configurable goals ?
Blueprint information
- Status:
- Complete
- Approver:
- Antoine Cabot
- Priority:
- Essential
- Drafter:
- David TARDIVEL
- Direction:
- Approved
- Assignee:
- Prashanth Hari
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
- Implemented
- Milestone target:
- newton-3
- Started by
- Antoine Cabot
- Completed by
- Vincent Françoise
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Author: hvprash <email address hidden> AuthorDate: 2016-05-16 19:02:19 -0400 Commit: hvprash <email address hidden> CommitDate: 2016-05-16 19:02:19 -0400
Gerrit topic: https:/
Addressed by: https:/
[WIP] Cancel out related audits and action plans
Addressed by: https:/
[WIP] Implement goal_id, strategy_id and host_aggregate into Audit api
Addressed by: https:/
Add goal_id, strategy_id and host_aggregate CLI options to an audit
Addressed by: https:/
WIP: Implement goal_id, strategy_id and host_aggregate into Audit api
Addressed by: https:/
Add new audit fields in dashboard tables
Work Items
Dependency tree
* Blueprints in grey have been implemented.