Closed Bug 1244297 Opened 6 years ago Closed 6 years ago
Telemetry server does not appear to be receiving "core" pings
Fresh Nightly installs fail to upload due to bug 1244295, but once client ID is created, the upload is claimed success in the logcat output. We upload to a url such as: <server>/submit/telemetry/643a141f-335f-4b0b-88a9-481d16ac4252/core/Fennec/47.0a1/default/20160129133745/ One theory is that the trailing slash is causing issues, but mreid thinks the server side code handles the edge case appropriately.
It looks like it was getting categorized as old telemetry and never made it to the new pipeline since 'v' != 4.
Assignee: michael.l.comella → mcomella
6 years ago
Assignee: mcomella → michael.l.comella
6 years ago
The server team pushed an update and the pings are visible on the server, however, there will more work before the pings are usable via spark – https://github.com/mozilla-services/data-pipeline/pull/183 has been merged but has yet to be deployed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
fyi, on S3, these pings are stored in a different place currently: aws s3 ls s3://<server-url>/telemetry-2/20160202/telemetry/UNKNOWN/core/Fennec/ where you can change 20160202 to different dates. The source location should be fixed with the pr in comment 2.
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.