Closed Bug 1760631 Opened 3 years ago Closed 2 months ago

Glean pipeline assumes all events will come form the 'events' ping, which Glean clients do not enforce

Categories

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

Product:
Data Platform and Tools
Component:
Glean: SDK
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: brizental, Unassigned)

References

Details

Discussion started after Glean.js implemented the 'events' ping, which prompted the pipeline to automatically generate a table that overwrote custom events tables on the VPN app.

See: https://mozilla.slack.com/archives/C4D5ZA91B/p1647627120789569 and https://github.com/mozilla/bigquery-etl/pull/2813/files

I think there is a misalignment that needs to be discussed here between Glean clients and the pipeline.

See Also: → 1760255
Component: Glean Platform → Glean: SDK

We continue to recommend sending events in the events ping, and when that isn't possible or feasible, then special care and work needs to be done on the downstream analyses to ensure the events are visible.

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.