[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:
Related
related to SERVER-4785 slowms should be per database for pro... Backlog
is related to SERVER-69485 Profiler setting of low "slowms" crea... Closed
is related to SERVER-17959 option to redact sensitive data from ... Closed
Assigned Teams:
Server Security
Participants:
Case:

 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).


Generated at Thu Feb 08 03:49:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.