[COMPASS-6772] Investigate changes in SERVER-75609: Fail more gracefully if computing telemetry key or storing telemetry fails Created: 26/Apr/23  Updated: 28/Jun/23  Resolved: 28/Jun/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-75609 Fail more gracefully if computing tel... Closed
Epic Link: COMPASS-6403
Documentation Changes: Not Needed

 Description   
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.



 Comments   
Comment by Anna Henningsen [ 28/Jun/23 ]

No DevTools impact.

Generated at Wed Feb 07 22:44:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.