Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-14065

Report live restore metrics on completion

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Live Restore
    • Storage Engines
    • 5
    • StorEng - Defined Pipeline

      We'd like to collect data on how live restore performs in Atlas, and for this we should output a log line at the end of live restore with important metrics.

      This ticket is for determining what metrics to output, how to collect them, and implementing the log line. We expect this to be picked up by a tools like the Atlas log ingestion service.

      As an example we could consider reporting:

      • Time to startup: Live Restore is intended get customers up and running quickly, so knowing how much time they'd save compared to the current process of copying the entire database from a backup should be reported
      • read/write latencies: A ballpark figure for how much slower the database is during live restore versus normal operation
      • Live restore duration: How long it took for live restore to completely migrate all data

      This list is not exhaustive.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            andrew.morton@mongodb.com Andrew Morton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: