ExportXMLWordPrintableJSON

    • DB Integration & Observability
    • Minor Change
    • ALL
    • v9.0
    • QI 2025-02-17
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The change stream aggregate command’s maxTimeMS and the cursor’s getMore maxAwaitTimeMS represent different options. The metric is intended to measure the cursor wait option (maxAwaitTimeMS), but its current name and test behavior can imply that it measures maxTimeMS on aggregate.

      Update the metric and its coverage so they reflect the intended option and match customer-facing terminology.

      We should do the following;

      • Update the Extend Change Streams Metrics design document to describe the intended cursor option.
      • Rename the metric `metrics.changeStreams.option.cursor.maxAwaitTimeMS` to `metrics.changeStreams.option.cursor.maxAwaitTimeMS`.
      • Update the test to verify the metric increments for getMore commands with maxAwaitTimeMS, and does not increment for aggregate commands with maxTimeMS.
      • Confirm whether the metric rename should be backported to v9.0, as discussed during the BF investigation.

      Acceptance criteria

      • The metric name and documentation identify it as the change stream cursor maxAwaitTimeMS option.
      • Tests cover the getMore increment and aggregate non-increment cases.
      • The backport decision for v9.0 is documented and followed.

            Assignee:
            Cian Nugent McGealy
            Reporter:
            Cian Nugent McGealy
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: