Investigate changes in SERVER-75609: Fail more gracefully if computing telemetry key or storing telemetry fails

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Done
    • Priority: Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed

      Original Downstream Change Summary

      Added two new serverStatus metrics, telemetry.numTelemetryStoreWriteErrors and telemetry.numRedactionErrors.

      Description of Linked Ticket

      We've had a couple instances where we either fail to collect telemetry for a certain query, or fail to redact a certain query. Currently failing to record telemetry tasserts - which would fail the operation in production. Failing to redact telemetry will tassert in a debug build, and log a warning in an optimized/release build. I think the recording logic (first one) should match this redaction logic (second one) to make it a bit safer.

              Assignee:
              Unassigned
              Reporter:
              Backlog - Core Eng Program Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: