Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13884

Investigate changes in SERVER-48742: Log whenever profiler settings are changed via setProfilingLevel

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.7.0, 4.4.2
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Downstream Change Summary

      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

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              backlog-server-pm Backlog - DB Eng Program Management Team
              Participants:
              Last commenter:
              Backlog - DB Eng Program Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Days since reply:
                4 weeks, 5 days ago