ExportXMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 9.1.0-rc0
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, in serverStatus metrics, we report only a few metrics for the FCV document:

      "featureCompatibilityVersion": {
          "transitioning": 0 // 0 = Steady, 1 = Upgrading, -1 = Downgrading
          "major": 9, // Target FCV is transitioning != 0, else Current FCV
          "minor": 0, // Target FCV is transitioning != 0, else Current FCV 
      },

       

      For debugging and dashboards, it would be helpful to also report metrics for the last setFCV command call, e.g.:

      "lastSetFCV": {
          "startedAt": "2026-12-25T01:23:45",
          "durationMillis": 42137,
          "previousVersion": "8.3",
          "newVersion": "9.0",
          "running": false, // If the setFCV command is running right now
                            // (different from the FCV doc. being transitional!)
          "status": 0,
      }

       

      This would let us:

      • Plot an histogram of setFCV durations
      • Distinguish "setFCV failed and left the FCV in transitioning state" vs "setFCV is running, just slow"
      • Narrow down how often and why setFCV fails
      • Etc.

       

      NOTE: On a further ticket/project we should add observability into phases/steps

            Assignee:
            Unassigned
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: