[SERVER-8359] Database changes are written to an audit log Created: 28/Jan/13 Updated: 15/Feb/13 Resolved: 28/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Matt Kalan | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Any configuration changes, in particular those that can be disruptive to the system, should be tracked to an audit log. Many organizations track database configuration and schema changes in RDBMSs and they would like an analogous tracking with Mongo. Because there is not a schema, at least changes to database, collections, and indexes would be tracked plus any database configuration, e.g. replica sets, sharding, etc. |