[SERVER-41735] Auditing Functionality for Mongo DB at DB level with triggers Created: 14/Jun/19 Updated: 14/Jun/19 Resolved: 14/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Raviteja Burugu | Assignee: | Eric Sedor |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
I want to create auditing in the Mongo DB which should be completely done at the DB level for the various actions using some triggers |
| Comments |
| Comment by Eric Sedor [ 14/Jun/19 ] |
|
Hi raviteja.burugu@nextbos.com, We are tracking the request for trigger functionality in SERVER-124, so I am going to close this ticket as a duplicate. Please watch that ticket for updates or add information about your use-case there. But I also wanted to let you know that current workarounds for this may include change streams or auditing, depending on what you needed to trigger on. But as you are probably aware this currently requires you to deploy a service to consume the results and initiate your desired activity |