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

"serverStatus was very slow" log message has unusual format

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Server Security
    • Service Arch 2023-12-11, Service Arch 2023-12-25

    Description

      The format says how much time has elapsed after each section rather than how much time each section takes individually. This makes it hard to run analytics on.

      [js_test:ldap_reaper] d20270| 2022-01-13T16:49:50.065+00:00 I  COMMAND  20499   [ftdc] "serverStatus was very slow","attr":{"timeStats":{"after basic":0,"after activeIndexBuilds":0,"after asserts":0,"after bucketCatalog":0,"after catalogStats":0,"after connections":0,"after electionMetrics":0,"after encryptionAtRest":0,"after extra_info":0,"after flowControl":0,"after globalLock":0,"after ldapConnPool":3388,"after ldapOperations":3388,"after locks":3388,"after logicalSessionRecordCache":3388,"after mirroredReads":3388,"after network":3388,"after opLatencies":3388,"after opcounters":3388,"after opcountersRepl":3388,"after oplogTruncation":3388,"after readConcernCounters":3388,"after repl":3388,"after scramCache":3388,"after security":3388,"after storageEngine":3388,"after tcmalloc":3388,"after tenantMigrations":3388,"after trafficRecording":3388,"after transactions":3388,"after transportSecurity":3388,"after twoPhaseCommitCoordinator":3388,"after wiredTiger":3388,"at end":3389}}
      

      Attachments

        Activity

          People

            backlog-server-security Backlog - Security Team
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: