I was expecting to start seeing a significant volume of beta traffic to the new data pipeline (which only sees v4 Telemetry data), but have not seen anything much so far. See https://pipeline-prototype-cep.prod.mozaws.net/#sandboxes/PrototypeSandbox-mreid_CountByChannel/outputs/PrototypeSandbox-mreid_CountByChannel.betaRequests.cbuf And the overall beta traffic to the old Telemetry backend (no noticeable recent change): http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/#sandboxes/TelemetryChannelMetrics60DaysAggregator/outputs/TelemetryChannelMetrics60DaysAggregator.beta.cbuf Note the change in submission patterns when v4 landed on Aurora: http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/#sandboxes/TelemetryChannelMetrics60DaysAggregator/outputs/TelemetryChannelMetrics60DaysAggregator.aurora.cbuf

We are starting to see a few more Beta submissions, but still nowhere near the expected volume.

A few observations: - Firefox Beta 39 just started rolling out on the 24th of May. See [1] - As of today, Firefox Beta 38 does not update to 39 (I guess updates are still rolling out). - As of today, the "Firefox Beta" download website just lets you download 38. I've got the link in [1] thanks to #firefox. That said, manually downloading the Firefox Beta 39 from [1] and running it seems to produce the expected behaviour: I'm able to generate pings (starting FF and installing an addon) and see them using the gzipServer [3] (main ping with environment-changed, saved-session and shutdown reasons). Building FF39 Beta from the Beta repository behaves the same way. Maybe we're starting to see more telemetry beta submissions now as 39 beta is spreading out? [1] - https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/39.0b1/ [2] - https://www.mozilla.org/en-US/firefox/beta/all/ [3] - https://github.com/georgf/gzipServer/

Firefox 38.0.5 was staged on the Beta channel until now

I'm still not getting updated to Beta 39. I think Beta will switch from 38.0.5 to 39 around June 2nd: https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates

We can probably close this off?