Closed
Bug 1242258
Opened 9 years ago
Closed 9 years ago
Get "core" pings out of the "OTHER" bucket
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gfritzsche, Assigned: mreid)
References
Details
(Whiteboard: [measurement:client:tracking])
Once bug 1205835 landed we should start receiving "core" pings from Android.
We should get them out of the "OTHER" bucket so we can look them up by document type etc.
Assignee | ||
Comment 1•9 years ago
|
||
Sent a PR to add this on the server:
https://github.com/mozilla-services/puppet-config/pull/1744
We should also update the metadata bucket with the updated schemas.
Reporter | ||
Updated•9 years ago
|
Assignee: nobody → mreid
Assignee | ||
Comment 4•9 years ago
|
||
Ok, I think all that's needed now is to deploy this change:
https://github.com/mozilla-services/data-pipeline/pull/183
Wesley, can you take care of that?
Flags: needinfo?(whd)
Comment 5•9 years ago
|
||
I attempted to deploy this today, but an unrelated code change that never got deployed (https://bugzilla.mozilla.org/show_bug.cgi?id=1227278) caused the executive summary to stop being sent and I had to roll back. This also means we need to backfill the executive summary for today as it's partially missing.
I will investigate in stage why the geoip city changes cause the executive summary to stop being extracted.
Flags: needinfo?(whd)
Comment 6•9 years ago
|
||
https://github.com/mozilla-services/data-pipeline/pull/185 has the fix needed to propagate the geoip city. Once that's merged I'll redeploy.
Comment 7•9 years ago
|
||
The fix was merged and redeployed, and I'm seeing files like:
telemetry/current/20160202/telemetry/1/core/Fennec/nightly/47.0a1/20160202030232
on the DWL nodes, so things are looking good.
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•