[SERVER-18946] I wish I can configure separately the profiler and log file Created: 12/Jun/15 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Logging, Security |
| Affects Version/s: | None |
| Fix Version/s: | Needs Further Definition |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ricardo Lorenzo | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Server Security
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
We have profiler option turned on in our MongoDB. Meanwhile, mongod. The instance continues to write information about slow operations to it's mongod.log file. From our perspective and according to our use case, it's useless to write actually identical data to both collection and log. In addition, in our case the profiler data contains customer sensitive data which actually leads to a problem in the mongod.log file management. It will be useful have the chance to setup differently the writes on the log file (for example, configuring a different value for the slow queries). |