[SERVER-75609] Fail more gracefully if computing telemetry key or storing telemetry fails Created: 03/Apr/23 Updated: 02/Feb/24 Resolved: 26/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Alyssa Clark |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 02/Feb/24 ] |
|
Author: {'name': 'Erin Zhu', 'email': 'erin.zhu@mongodb.com', 'username': 'erinzhu001'}Message: Includes community changes from and enterprise changes from GitOrigin-RevId: f424d1b1848f85581a870c061b1231219748c00c |
| Comment by Githook User [ 26/Apr/23 ] |
|
Author: {'name': 'Alyssa Wagenmaker', 'email': 'alyssa.wagenmaker@mongodb.com', 'username': 'awagenmaker'}Message: |
| Comment by Charlie Swanson [ 21/Apr/23 ] |
|
Unlinking from |