-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
Affects Version/s: None
-
None
-
Server Security
-
(copied to CRM)
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).
- is related to
-
SERVER-69485 Profiler setting of low "slowms" creates huge log file
- Closed
-
SERVER-17959 option to redact sensitive data from system logs
- Closed
- related to
-
SERVER-4785 slowms should be per database for profiler
- Backlog