Closed Bug 1570932 Opened 4 months ago Closed 3 months ago

Add telemetry about how often we observe network change events

Categories

(Core :: Networking, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: dragana, Assigned: michal)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(2 files, 1 obsolete file)

No description provided.
Priority: -- → P2
Whiteboard: [necko-triaged]

Nhi can you find someone to work on this?

Flags: needinfo?(nhnguyen)
Assignee: nobody → michal.novotny
Flags: needinfo?(nhnguyen)
Priority: P2 → P1
Attachment #9088878 - Flags: data-review?(chutten)
Comment on attachment 9088878 [details]
Request for data collection review form

Load-balance to :teon.
Attachment #9088878 - Flags: data-review?(chutten) → data-review?(teon)
Comment on attachment 9088878 [details]
Request for data collection review form

:michal will you be responsible for either renewing or turning off the collection with Fx 76?
Flags: needinfo?(michal.novotny)

Yes. I assume there will be an email notification.

Flags: needinfo?(michal.novotny)
Comment on attachment 9088878 [details]
Request for data collection review form

DATA COLLECTION REVIEW RESPONSE:

    Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes. This collection is Telemetry so is documented in its definitions file [Events.yaml](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Events.yaml) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/).

    Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

    If the request is for permanent data collection, is there someone who will monitor the data over time?

No. This collection will expire in Fx76.

    Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1, Technical.

    Is the data collection request for default-on or default-off?

Default on for pre-release channels only.

    Does the instrumentation include the addition of any new identifiers?

No.

    Is the data collection covered by the existing Firefox privacy notice?

Yes.

    Does there need to be a check-in in the future to determine whether to renew the data?

Yes. :michal is responsible for renewing or removing the collection before it expires <when>.

---
Result: datareview
Attachment #9088878 - Flags: data-review?(teon) → data-review+

(In reply to Michal Novotny [:michal] from comment #6)

Yes. I assume there will be an email notification.

Unfortunately, at present there are no expiry emails sent for Telemetry Events. The system that sends expiry emails was built when it only had Histograms to worry about.

Sorry about that.

Attachment #9088743 - Attachment is obsolete: true
Keywords: checkin-needed

Pushed by ccoroiu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f592a66e8aba
Add telemetry about how often we observe network change events, r=dragana

Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Blocks: 1587932

Dragana noticed that the distribution on TMO showed a lot of events in the underflow bucket (time < 1000 ms) for MacOS: https://mzl.la/2ovzvZD

Nhi asked me to look at whether this showed up at the user level.

Query: https://sql.telemetry.mozilla.org/queries/65284/source

About a quarter of MacOS client-days included at least one network change bounce (time between events less than 1 second). If a client-day on Mojave contained any bounces, the median number of bounces was 2 and the mean was 22. The 95th percentile of bounces in a single client-day was 27 and the maximum number observed was 5,160.

There were no obvious differences between recent OS versions.

Neither Linux or Windows show nearly as many events in the underflow bucket.

You need to log in before you can comment on or make changes to this bug.