We now log whenever the profile settings (level, slowms, sampleRate, filter) change at runtime (which happens via the profile command).
Description of Linked Ticket
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.
Scope of changes
Suggest updating https://docs.mongodb.com/manual/reference/command/profile/#behavior and https://docs.mongodb.com/manual/reference/method/db.setProfilingLevel/index.html to reflect this new behavior, along with the usual release notes update. There may be other places to doc this behavior, but those are the first pages which come to mind.
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- backported by
DOCS-14056 [BACKPORT] [v4.2] Log whenever profiler settings are changed via setProfilingLevel
DOCS-14057 [BACKPORT] [v4.0] Log whenever profiler settings are changed via setProfilingLevel
SERVER-48742 Log whenever profiler settings are changed via setProfilingLevel