Report workingMillis in serverStatus opLatencies

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 8.0.0-rc6
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • v8.0
    • Execution Team 2024-04-29, Execution Team 2024-05-13, Execution Team 2024-05-27
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      From isabel.peters@mongodb.com:

      Our system on Cloud Intel to dynamically adjust the profilerLevel slowms value for customer clusters uses serverStatus.opLatencies to determine what the slowms value should be set to for collecting slowlogs. I have just learned that the serverStatus.opLatencies will remain based off durationMillis rather than workingMillis in 8.0 which would be a problem for the system to accurately determine the right profiling slowms threshold

      Would it be possible to add opLatencies based off workingMillis in the serverStatus response as well?

      We may want to consider adding a different serverStatus section rather than changing the meaning of opLatencies.

            Assignee:
            Shin Yee Tan
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: