Closed
Bug 1200164
Opened 9 years ago
Closed 8 years ago
Only do isOfficialTelemetry checks for Telemetry upload
Categories
(Toolkit :: Telemetry, defect, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
People
(Reporter: Dexter, Assigned: gfritzsche)
References
(Blocks 1 open bug)
Details
(Whiteboard: [measurement:client])
Attachments
(2 files, 1 obsolete file)
1.70 KB,
patch
|
benjamin
:
review-
|
Details | Diff | Splinter Review |
6.29 KB,
patch
|
gfritzsche
:
review+
|
Details | Diff | Splinter Review |
Throughout the Telemetry code we disable some behaviours (e.g. the creation of shutdown pings and the deletion of aborted session pings [1]) if we're not running an official build (both MOZILLA_OFFICIAL and MOZ_TELEMETRY_REPORTING are set). This could cause some confusion during debugging sessions: I think we should restrict those checks only to ping uploads. [1] - https://dxr.mozilla.org/mozilla-central/rev/f2518b8a7b97b5bb477e94bc9131584007aac887/toolkit/components/telemetry/TelemetrySession.jsm#1792
Reporter | ||
Updated•9 years ago
|
Blocks: 1122482
status-firefox41:
--- → affected
status-firefox42:
--- → affected
Whiteboard: [unifiedTelemetry]
Reporter | ||
Comment 2•9 years ago
|
||
More info about this can be found in bug 1173720 comment 2.
Reporter | ||
Updated•9 years ago
|
Assignee | ||
Updated•9 years ago
|
Points: --- → 2
Priority: -- → P3
Whiteboard: [unifiedTelemetry] → [unifiedTelemetry] [measurement:client]
Assignee | ||
Updated•9 years ago
|
Priority: P3 → P2
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → gfritzsche
Priority: P2 → P1
Whiteboard: [unifiedTelemetry] [measurement:client] → [measurement:client]
Assignee | ||
Comment 3•9 years ago
|
||
Attachment #8698909 -
Flags: review?(alessio.placitelli)
Assignee | ||
Comment 4•9 years ago
|
||
Attachment #8698910 -
Flags: review?(benjamin)
Reporter | ||
Comment 5•9 years ago
|
||
Comment on attachment 8698909 [details] [diff] [review] Only do isOfficialTelemetry checks for Telemetry uploads Review of attachment 8698909 [details] [diff] [review]: ----------------------------------------------------------------- This looks good and... much appreciated! ::: toolkit/components/telemetry/docs/preferences.rst @@ +9,1 @@ > Sending only happens on official builds with ``MOZ_TELEMETRY_REPORTING`` defined. Nit: Maybe we should keep/mention that official means "defining MOZILLA_OFFICIAL" here.
Attachment #8698909 -
Flags: review?(alessio.placitelli) → review+
Assignee | ||
Comment 6•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Attachment #8698909 -
Attachment is obsolete: true
Assignee | ||
Updated•9 years ago
|
Attachment #8699956 -
Flags: review+
Comment 7•8 years ago
|
||
Comment on attachment 8698910 [details] [diff] [review] Make developer builds always default to Telemetry enabled I don't think this is a good idea. There are many other uses for MOZILLA_OFFICIAL beyond developer builds: I suspect this will affect various linux distros, for example. I also don't see why it's especially important to have extended-set telemetry on by default for developer builds.
Attachment #8698910 -
Flags: review?(benjamin) → review-
Assignee | ||
Comment 8•8 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #7) > I don't think this is a good idea. There are many other uses for > MOZILLA_OFFICIAL beyond developer builds: I suspect this will affect various > linux distros, for example. > > I also don't see why it's especially important to have extended-set > telemetry on by default for developer builds. I think it would be much better to match the Nightly Telemetry behavior in Firefox dev builds (i.e. default to Telemetry on), some points here are: * it avoids confusion ("oh, this hasn't recorded yet because Telemetry isn't on!") * it gives dev builds the same behavior here * it avoids issues with tests (test blowing up on CI that worked fine in local build due to different defaults) Do you agree with this if we have a better solution without the side-effects you brought up?
Flags: needinfo?(benjamin)
Assignee | ||
Comment 9•8 years ago
|
||
Part 1 pushed to try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=e288cbadf1ea
Assignee | ||
Updated•8 years ago
|
Keywords: leave-open
Comment 11•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/762e4af55ba2
Comment 12•8 years ago
|
||
In theory if you could have nightly developer builds turn extended collection on (without any sending), while at the same time not change the defaults for external distributors building releases from tarballs, that would be fine. I don't know how specifically you'd accomplish that though.
Flags: needinfo?(benjamin)
Assignee | ||
Comment 13•8 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #12) > In theory if you could have nightly developer builds turn extended > collection on (without any sending), while at the same time not change the > defaults for external distributors building releases from tarballs, that > would be fine. I don't know how specifically you'd accomplish that though. Right, ok - that doesn't sound easily doable, moved this to bug 1237954 for consideration.
Assignee | ||
Updated•8 years ago
|
status-firefox41:
affected → ---
status-firefox42:
affected → ---
status-firefox43:
affected → ---
status-firefox45:
--- → wontfix
status-firefox46:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•