[SERVER-48742] Log whenever profiler settings are changed via setProfilingLevel Created: 11/Jun/20  Updated: 29/Oct/23  Resolved: 30/Jun/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.7.0, 4.4.2, 4.0.22, 4.2.12

Type: New Feature Priority: Critical - P2
Reporter: David Percy Assignee: Andrii Dobroshynskyi (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng, qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-13884 Investigate changes in SERVER-48742: ... Closed
Problem/Incident
causes SERVER-70249 Log database name when profiler setti... Closed
Related
is related to SERVER-55069 include operationProfiling parameter ... Backlog
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2, v4.0, v3.6
Sprint: Query 2020-06-29, Query 2020-07-13
Participants:

 Description   

We should add a log message, at log level 0, whenever the server's profiling settings are changed at run-time. The typical way you change these settings is via the setProfilingLevel shell helper: https://docs.mongodb.com/manual/reference/method/db.setProfilingLevel/index.html

This will make it easier to understand log files. The server logs slow queries to the log file, using the profiling setting to decide what 'slow' means. For someone digging through a log file, and seeing the number of slow queries suddenly go up or down, it might be helpful to know whether that's because the workload changed or the profiling settings changed.



 Comments   
Comment by Githook User [ 10/Dec/20 ]

Author:

{'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}

Message: SERVER-48742 Modified 4.4 backport to remove dependence on structured logging
Branch: v4.2
https://github.com/mongodb/mongo/commit/e7df7aee5095174712f8b73ac2fa4c8d6afa0293

Comment by Githook User [ 10/Dec/20 ]

Author:

{'name': 'Andrii Dobroshynskyi', 'email': 'andrii.dobroshynskyi@mongodb.com'}

Message: SERVER-48742 Log changes to profiler settings

(cherry picked from commit 0d30729722165f15e52db2c02ebb56cfd1c6ccc1)
Branch: v4.2
https://github.com/mongodb/mongo/commit/f94f958425b488b305c943af156d33e39de4b28c

Comment by Githook User [ 11/Sep/20 ]

Author:

{'name': 'Andrii Dobroshynskyi', 'email': 'andrii.dobroshynskyi@mongodb.com'}

Message: SERVER-48742 Log changes to profiler settings
Branch: v4.4
https://github.com/mongodb/mongo/commit/0d30729722165f15e52db2c02ebb56cfd1c6ccc1

Comment by Githook User [ 02/Jul/20 ]

Author:

{'name': 'Andrii Dobroshynskyi', 'email': 'andrii.dobroshynskyi@mongodb.com'}

Message: SERVER-48742 Log changes to profiler settings
Branch: master
https://github.com/mongodb/mongo/commit/ecefb4ecaa80e56f0d87d70776850236439ab5ca

Comment by Githook User [ 30/Jun/20 ]

Author:

{'name': 'Eric Cox', 'email': 'eric.cox@mongodb.com', 'username': 'ericox'}

Message: Revert SERVER-48742 Log changes to profiler settings
Branch: master
https://github.com/mongodb/mongo/commit/6d650280c2d21c24dc2c45d1d41e915f4d244ffa

Comment by Githook User [ 30/Jun/20 ]

Author:

{'name': 'Andrii Dobroshynskyi', 'email': 'andrii.dobroshynskyi@mongodb.com'}

Message: SERVER-48742 Log changes to profiler settings
Branch: master
https://github.com/mongodb/mongo/commit/7917051ba59a15fddf70493ffe50ec28289523ae

Generated at Thu Feb 08 05:17:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.