-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Networking & Observability
-
Service Arch 2023-12-11, Service Arch 2023-12-25, Security 2024-03-18, Security 2024-04-01, Security 2024-04-15, Security 2024-04-29, Security 2024-05-13, Security 2024-05-27, Security 2024-06-24, Server Security 2025-04-28
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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}}
- is duplicated by
-
SERVER-101196 Reformat serverStatus was very slow log and its timing section counterpart
-
- Closed
-
- is related to
-
-
- Open
-
- related to
-
SERVER-77875 Create stall monitor for all commands that Cloud Monitoring uses
-
- Closed
-