Following up to bug 1284652, we need to whitelist the "outofdate-notifications-system-addon" ping type. (In reply to Matt Howell [:mhowell] from comment #0) > As part of bug 1280378 we're adding a new unified telemetry ping type that > needs to be ingested and made available for analysis. A custom ping is > needed because this is part of a system add-on which will be installed in > old browser versions, so just adding a new histogram is not possible. > > To summarize, with the current code the pings are sent using > submitExternalPing() with type "outofdate-notifications-system-addon", > clientID enabled, and the payload: > > { > shown: <bool>, > clicked: <bool> > } > > See [1] for the documentation and code. bsmedberg has reviewed those > materials, so I think the data collection policy requirements are satisfied. > I've never done this before; not sure what else is needed. > > [1] https://github.com/mozilla/outofdate-notifications-system-addon

The payload & submission changed over in bug 1284652. The payload is now: {event:"started"|"shown"|"clicked"} This now submits at most 3 pings per Firefox session (one of each event type). Bug 1284652, comment 4 describes the population size that would submit these pings: > The most recent analysis using the 1% longitudinal dataset shows a total > number of 27,873 users on Firefox 44 with updates enabled, so it would be > reasonable to expect about 2,787,300 users to download this system addon and > send pings. mreid, is this fine given the small payload, submission limit and limited population?

I don't foresee a problem with the ping volume with a population of ~3M submitting up to 3 pings per session. I'll add the whitelist change presently.

Sent PR https://github.com/mozilla-services/puppet-config/pull/2204