Closed Bug 1579522 Opened 1 year ago Closed 1 year ago

Don't send the "modules" ping within the first 30min of a profile's first session

Categories

(Toolkit :: Telemetry, task, P1)

task
Points:
2

Tracking

()

RESOLVED FIXED
mozilla71
Tracking Status
firefox71 --- fixed

People

(Reporter: chutten, Assigned: chutten)

References

Details

Attachments

(2 files)

Conversation starts here: https://bugzilla.mozilla.org/show_bug.cgi?id=1576948#c5

In summary, the "modules" ping is registered to a weekly cadence. The first tick in that cadence happens about 10-15min into the first session of a new profile. It doesn't need to happen at all that first week, let alone that first session. (see bug 1576948 comment 9)

So let's delay it somehow for some length of time. I can think of three options in decreasing pleasantness to implement:

  1. Don't register the timer at all in that first session (by checking TelemetryReportingPolicy's isFirstRun. Might have to rewire it slightly to be a static pref getter because the value isn't correct until session restore's complete.)
  2. Modify the update timer manager such that the first tick is configurable. (Specifically make this part optional.)
  3. Store some state in ModulesPing to ignore timer ticks that happen to early. (Probably would involve adding a pref)
Assignee: nobody → chutten
Status: NEW → ASSIGNED
Points: --- → 2
Priority: -- → P1

The UpdateTimerManager has an undocumented behaviour for firing its listeners
very soon after first registration (about 10min into the first session).

Let's document that behaviour, and make it optional.

Pushed by chutten@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fb1c3bf44fb1
Allow skipping first update timer interval r=kmag
https://hg.mozilla.org/integration/autoland/rev/229c49ee94df
Don't trigger a "modules" ping in the first session r=janerik,aklotz

Well that's odd. It appears to be attempting a network connection? That... doesn't make sense. And to au5.mozilla.org? The host that serves updates?

Not sure what this has to do with... ohhhhhh... maybe by futzing with the update timer manager I caused the other registered timers to bork somehow? Clearly I need to add more tests to update timer manager.

Flags: needinfo?(chutten)

There are some r+ patches which didn't land and no activity in this bug for 2 weeks.
:chutten, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(chutten)

Thanks auto_nag. I've been busy, and the r+ patches were backed out. I'm working on it now (oh why am I talking to a bot)

Flags: needinfo?(chutten)
Attachment #9093590 - Attachment description: Bug 1579522 - Allow skipping first update timer interval r?kmag! → Bug 1579522 - Allow skipping first update timer interval r=kmag
Attachment #9093591 - Attachment description: Bug 1579522 - Don't trigger a "modules" ping in the first session r?janerik!,aklotz! → Bug 1579522 - Don't trigger a "modules" ping in the first session r=janerik,aklotz
Pushed by chutten@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a69f8d7d2a53
Allow skipping first update timer interval r=kmag
https://hg.mozilla.org/integration/autoland/rev/fdc947cae3e5
Don't trigger a "modules" ping in the first session r=janerik,aklotz
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in before you can comment on or make changes to this bug.