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

Make latency histogram collection optional in full-time diagnostic data capture

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.12
    • Affects Version/s: None
    • Component/s: Diagnostics, Querying
    • None
    • Fully Compatible
    • Integration 2016-09-19

      The new latency histogram facility adds a considerable amount of data to ftdc, decreasing the retention period significantly. It has limited value for the primary purpose of always-on ftdc, because mongod logs provide information about the high-latency operations which are generally of interest for after-the-fact issue analysis. Collection of latency histogram data by ftdc should be optional, off by default. It should be possible to enable capture of latency histogram data in ftdc dynamically at runtime if desired to use it for targeted performance investigations.

            Assignee:
            kyle.suarez@mongodb.com Kyle Suarez
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: