Closed Bug 2059503 Opened 3 months ago Closed 3 months ago

schema error in `org_mozilla_firefox` for #/client_info/glean.error.invalid_overflow

Categories

(Data Platform and Tools :: Glean: SDK, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: benwu, Assigned: janerik)

References

Details

(Whiteboard: [dataquality])

Attachments

(1 external file)

On 2026-07-16 we started getting schema errors ingestion with the message #/client_info: extraneous key [glean.error.invalid_overflow] is not permitted. It seems to only org-mozilla-firefox on version 153 and across all ping types. https://sql.telemetry.mozilla.org/queries/124074/source

Digging into the payloads: https://sql.telemetry.mozilla.org/queries/124079/source

They look like {"client_info": {"glean.error.invalid_overflow":{"attribution.content":1}}} so they're being stored in client_info instead of metrics. I'm not sure if this is a new bug or latent one just because we weren't getting many overflows, but it seems like an SDK bug and I didn't find any evidence of fixes.

Looker for error counts: https://mozilla.cloud.looker.com/x/O7S1O1EbJlDjBma89KdAtd

Note that this error cause pings to be dropped because client_info doesn't allow additional_properties but it's affecting <0.01% of pings for most ping types. play_store_attribution_v1 and first_session_v1 are higher at ~0.37% and ~0.12%

That's a genuine bug due to how we record errors and how attribution is implemented.
Guess it's not THAT big of a problem right now due to attribution values being mostly fixed to known strings.

I'll fix the underlying issue.

Assignee: nobody → jrediger
Status: NEW → ASSIGNED
Priority: -- → P1
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
See Also: → 2079526
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: