Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48742

Log whenever profiler settings are changed via setProfilingLevel

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • None
    • 4.7.0, 4.4.2, 4.0.22, 4.2.12
    • None
    • Fully Compatible
    • v4.4, v4.2, v4.0, v3.6
    • Query 2020-06-29, Query 2020-07-13

    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.

      Attachments

        Issue Links

          causes

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-70249 Log database name when profiler settings are changed

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-13884 Investigate changes in SERVER-48742: Log whenever profiler settings are changed via setProfilingLevel

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-55069 include operationProfiling parameter values in serverStatus

          • Major - P3 - Major loss of function.
          • Backlog

          Activity

            People

              andrii.dobroshynskyi@mongodb.com Andrii Dobroshynskyi (Inactive)
              david.percy@mongodb.com David Percy
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: