Ignore pings from `org-mozilla-vrbrowser-internal` namespace
Categories
(Data Platform and Tools :: General, defect)
Tracking
(Not tracked)
People
(Reporter: benwu, Assigned: benwu)
Details
(Whiteboard: [dataquality])
org-mozilla-vrbrowser-internal
was found in the weekly health check missing namespaces: https://console.cloud.google.com/bigquery?sq=630180991450:2158680874ed4200bb12e4f13e9b180f
If this is a real Mozilla app and the data is needed then it should be added to glean applications. Otherwise it should be scrubbed. A related bug, bug 1614410, was filed for org-mozilla-vrbrowser-dev
.
Assignee | ||
Comment 1•3 years ago
|
||
Mike, is vrbowser still supported? Who could we check with to verify this data isn't needed?
Comment 2•3 years ago
|
||
The internal
suffix seems to be added for builds that don't ship to the Google Play Store (so, developer builds or custom builds). This isn't our recommended way to handle this -- we suggest tagging the pings instead so they still end up in the tables -- but it's not a big deal. I think it's safe to add a rule to just ignore these pings.
To the larger question about whether vrbrowser
should still be collecting telemetry at all, I think that's an important question, but will take some more time to answer. I'll take on asking the right folks, and I'm leaving my ni? open to come back to.
Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Updated•2 years ago
|
Description
•