Build Framework for Unique WT Verbose IDs & Update Critical Atlas Log Rules

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines, Storage Engines - Transactions
    • SE Transactions - 2025-07-18
    • 8
    • v8.0

      The acceptance criteria for this ticket are as follows:

      1. Implement a framework to propagate unique IDs from all WiredTiger verbose messages to MongoDB.
      2. Assign a default unique ID to all WiredTiger verbose messages.
      3. Update the Atlas log rules for recovery (671803d4d9b1133e33749aff) and shutdown (6617e1a152e9bc5241ffa846) to leverage the new unique ID.

       

      FYI. Here are the Atlas log rules.

      • 671803d4d9b1133e33749aff - WiredTiger message.(recovery) was completed successfully and took ([6-9]\d {4,}|\d{6,})ms, including ([\d])ms for the log replay, ([\d])ms for the rollback to stable, and ([\d])ms for the checkpoint.
      • 6617e1a152e9bc5241ffa846 - WiredTiger message.(shutdown) was completed successfully and took ([6-9]\d{4,}|\d{6,})ms, including ([\d]+)ms for the rollback to stable, and ([\d])ms for the checkpoint

      https://cloud.mongodb.com/v2/admin#/atlas/logIngestion

              Assignee:
              Ravi Giri
              Reporter:
              Ravi Giri
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: