[DOCS-16071] Investigate changes in SERVER-75609: Fail more gracefully if computing telemetry key or storing telemetry fails Created: 26/Apr/23 Updated: 13/Nov/23 Resolved: 02/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 7.1.0-rc0 |
| Fix Version/s: | 7.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Kenneth Dyer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | query, release | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 41 weeks ago | ||||||||
| Description |
|
Original Downstream Change Summary Added two new serverStatus metrics, telemetry.numTelemetryStoreWriteErrors and telemetry.numRedactionErrors. Description of Linked TicketWe'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. |