6.76 KB, text/plain
We noticed that the submissions from "Other" channels (in this case, ones that are not "release", "beta", "aurora", or "nightly") are on the rise. Corroborated at both  and . My theory is that it could be due to Unified Telemetry landing in the Extended Support Release (esr) channel. In order to check that, we should filter by normalized channel == 'Other', then group the submissions by the actual channel name in the payload (for main pings, this would be found in the `application.channel` part of the payload.  https://sql.telemetry.mozilla.org/queries/81/source#127  https://metrics.services.mozilla.com/telemetry-budget-dashboard/  https://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/common-ping.html
Assignee: nobody → rharter
Priority: -- → P2
Created attachment 8803328 [details] List of Channels for 20161019 by ping count and size I had a notebook with easy access to this data already, so adding it for posterity.
Since this has sat for a while, I want to confirm we're talking about the increase in Other Pings that appears to start on 2016-06-10 . It looks like peak Other Pings appear to roughly double in a week. This event is now out of range on the budget dashboard  We can verify this question with STMO . It looks like the increase in Other Pings is clearly from increasing ESR pings. As always, a plot is worth a thousand words: https://raw.githubusercontent.com/harterrt/other_pings_investigation/master/other_pings_investigation.png https://drive.google.com/open?id=0Bxe938oq1vUJV1Zpbzlad0NFX0E https://drive.google.com/open?id=0Bxe938oq1vUJTlUwZFNKeWpqUEU  Plot showing ESR increase: https://raw.githubusercontent.com/harterrt/other_pings_investigation/master/other_pings_investigation.png  Supporting R code: https://github.com/harterrt/other_pings_investigation/blob/master/main.R  Supporting STMO query: https://sql.telemetry.mozilla.org/queries/1549/source#table
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.