:wbeard noticed that some clients in the release channel are sending the MEMORY_TOTAL probe, which was (before Bug 1511918, which won't land until 66) supposed to be limited to prerelease only. We're consistently receiving a few hundred pings a day from clients that represent to be part of the release population but are sending us values for MEMORY_TOTAL and other prerelease-only probes. dbfs:/tdsmith/weird_pings.json contains release channel pings containing MEMORY_TOTAL from a single day during the 63 release, extracted by https://dbc-caf9527b-e073.cloud.databricks.com/#notebook/52325/command/52339. :chutten pointed out that we used to see O(millions) of these clients/day, so the step down to O(hundreds) is itself interesting: https://mzl.la/2Q7aEYC This doesn't block anything but is a little unnerving!
We have a pref for overriding the reported channel (toolkit.telemetry.overrideUpdateChannel) and another test preference (toolkit.telemetry.testing.overridePreRelease) for overriding the release/prerelease split, so maybe they're some possible culprits. P1 so it shows in my list at the top of 2019.
Assignee: nobody → chutten
Status: NEW → ASSIGNED
Priority: -- → P1
Points: --- → 2
Comment on attachment 9038047 [details] data collection review request General Notes: Seems low risk and straightforward, good sleuthing here! 1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate? Yes, pretty clear in Bug 1514031 plus TelemetryEnvironment.jsm is quite parsable 2) Is there a control mechanism that allows the user to turn the data collection on and off? Yes, Telemetry Defaults 3) If the request is for permanent data collection, is there someone who will monitor the data over time? 6 months collection by chutten 4) Using the category system of data types (https://wiki.mozilla.org/Firefox/Data_Collection), what collection type of data do the requested measurements fall under? Category 1, only what 2 low risk prefs are user set 5) Is the data collection request for default-on or default-off? Telemetry Defaults 6) Does the instrumentation include the addition of any *new* identifier* (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)? No 7) Is the data collection covered by the existing Firefox privacy notice? Yes, standard Telemetry 8) Does there need to be a check-in in the future to determine whether to renew the data? No
Attachment #9038047 - Flags: review?(rrayborn) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/cd4f8f60d10c Record the value of some telemetry testing prefs. r=janerik
Assignee: chutten → nobody
Status: RESOLVED → REOPENED
Points: 2 → ---
Priority: P1 → --
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 6 months ago → 3 months ago
Resolution: --- → FIXED
Assignee: nobody → chutten
You need to log in before you can comment on or make changes to this bug.