Problem:
A frequent request is to log any "DDL" operation that occurs
– drop collection
– ensureIndex
– dropIndex
– etc.
This would allow an organization to audit these changes, info the could be recorded would be
– operation
– date / time
– client connection (hostname, ip)
– etc.
Solution:
There are a couple of possible way this could work
- Log these operations into the existing log file
- Log these operations into a Capped Collection (but will impact DB throughput)
- Log these operations into a new audit log file
- is depended on by
-
DOCS-1834 Document Auditing "DDL" operations
-
- Closed
-
-
SERVER-11028 shutdown on Audit failure
-
- Closed
-
-
SERVER-4321 MongoDB Logging Related Issue
-
- Closed
-
- is duplicated by
-
SERVER-8359 Database changes are written to an audit log
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-11192 Audit system cannot ascribe DDL operations in a sharded cluster to an end user.
-
- Closed
-
-
-
- Closed
-