Measure opLatencies with workingMillis

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      opLatencies are currently set with durationMillis here and here. It might make sense to exclude lock and ticket wait times from opLatencies similar to workingMillis. We may consider adding another metric like opDuration that continues reporting based on durationMillis.

            Assignee:
            Shin Yee Tan
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: