[SERVER-34135] Option to write audit data to a capped collection Created: 26/Mar/18 Updated: 14/Aug/18 Resolved: 22/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Shakir Sadikali | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
We currently support writing audit records to syslog, JSON output, or BSON output. It would be nice to allow this data to be written to the database for additional functionality (i.e. tailable cursors or change streams for audit based alerting). |
| Comments |
| Comment by Shakir Sadikali [ 17/Jul/18 ] |
|
Hi Kelsey, I think it is covered by SERVER-12670 assuming we allow it include directing audit output to a collection in the source database as well. |
| Comment by Kelsey Schubert [ 26/Mar/18 ] |
|
shakir.sadikali, I think this is covered by SERVER-12670. Would you agree? |