Closed Bug 1745744 Opened 4 years ago Closed 4 years ago

Investigate Invalid Value errors observed from MozillaVPN clients after Glean update

Categories

(Data Platform and Tools Graveyard :: Glean.js, defect, P1)

Product:
Data Platform and Tools Graveyard
Component:
Glean.js
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: brizental, Assigned: brizental)

Details

https://sql.telemetry.mozilla.org/queries/83248/source#206337

Invalid Value errors are thrown for events when there is an attempt to record an extra key which is not allowed.

Priority: P4 → P2
Whiteboard: [telemetry:glean-js:m?]
Assignee: nobody → brizental
Priority: P2 → P1

Invalid Value errors are thrown for events when there is an attempt to record an extra key which is not allowed.

Looking at this with fresh eyes, I think it's very unlikely this is the problem.

Turns out we also record an error when the timestamp on this specific metric is negative, which is much more likely to be the problem here. The glean.restarted event metric is created and recorded only by Glean internally. So recording an invalid key would be very unexpected.

I don't think there is much we can do about this though, so I'll close this bug for now.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in before you can comment on or make changes to this bug.