-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
Fully Compatible
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.
- is depended on by
-
SERVER-85099 Tracking: Milestone 1
- Closed
-
SERVER-85105 Tracking: PM-2885 Milestone 0
- Closed
-
COMPASS-6772 Investigate changes in SERVER-75609: Fail more gracefully if computing telemetry key or storing telemetry fails
- Closed
-
TOOLS-3291 Investigate changes in SERVER-75609: Fail more gracefully if computing telemetry key or storing telemetry fails
- Closed