Closed
Bug 1369844
Opened 7 years ago
Closed 7 years ago
Add a "kill-switch" switchboard flag for Sync Ping
Categories
(Firefox for Android Graveyard :: Metrics, enhancement, P1)
Firefox for Android Graveyard
Metrics
Tracking
(firefox55 fixed)
RESOLVED
FIXED
Firefox 55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: Grisha, Assigned: Grisha)
References
Details
Attachments
(1 file)
I anticipate that if anything's going to give us grief with Bug 1308337 landing, it's the "bundle, persist and upload" bits. This bug tracks putting that functionality behind a flipped-on switchboard flag, so that we're on a safe side of landing that patch series.
Comment hidden (mozreview-request) |
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → gkruglov
Status: NEW → ASSIGNED
Priority: -- → P1
Assignee | ||
Comment 2•7 years ago
|
||
I've considered adding multiple flags for more granular control - processing, storage, upload - but I think this is "good enough" and doesn't pose a threat of creating a dangerous combination of flags (e.g. process, store but never upload).
Comment 3•7 years ago
|
||
mozreview-review |
Comment on attachment 8875502 [details] Bug 1369844 - Add switchboard experiment for background telemetry processing https://reviewboard.mozilla.org/r/146932/#review151356 I'd like to see this again after clarifying how it's really going to work: enabled/disabled by default? Is it a "kill-switch" that you flip "on" for "kill" or that you flip "off" to "kill"? ::: mobile/android/base/java/org/mozilla/gecko/Experiments.java:80 (Diff revision 1) > public static final String FULL_BOOKMARK_MANAGEMENT = "full-bookmark-management"; > > // Enable Leanplum SDK > public static final String LEANPLUM = "leanplum-start"; > > + // Telemetry Background Ping Processing. We should follow suit with the file and use "enable" or "disable" in the comment consider. I think we should use the same word in the name and the string, too -- if the default is "enable" and this is a kill-switch, let's call it "disable" throughout. ::: mobile/android/base/java/org/mozilla/gecko/telemetry/TelemetryBackgroundReceiver.java:90 (Diff revision 1) > > @Override > public void onReceive(final Context context, final Intent intent) { > Log.i(LOG_TAG, "Handling background telemetry broadcast"); > > + if (!SwitchBoard.isInExperiment(context, Experiments.TELEMETRY_PROCESSING_BACKGROUND_PINGS)) { So, clearly something needs to be communicated. Is the default state "enabled" (from the Switchboard server)?
Attachment #8875502 -
Flags: review?(nalexander) → review-
Assignee | ||
Comment 4•7 years ago
|
||
(In reply to Nick Alexander :nalexander from comment #3) > I think we should use the same word in the name and the string, too -- if > the default is "enable" and this is a kill-switch, let's call it "disable" > throughout. I'm fine with either approach - default enabled for 100% of users, or default disabled for 0% of users. I slightly prefer to not have double negations ("not enabled for noone"), but I don't feel strongly about it.
Comment hidden (mozreview-request) |
Comment 6•7 years ago
|
||
mozreview-review |
Comment on attachment 8875502 [details] Bug 1369844 - Add switchboard experiment for background telemetry processing https://reviewboard.mozilla.org/r/146932/#review151546 ::: mobile/android/base/java/org/mozilla/gecko/Experiments.java:81 (Diff revision 2) > > // Enable Leanplum SDK > public static final String LEANPLUM = "leanplum-start"; > > + // Enable processing of background telemetry. > + public static final String ENABLE_PROCESSING_BACKGROUND_TELEMETRY = "process-background-telemetry"; nit: I'd prefer FOO_BAR_BAZ to agree with "foo-bar-baz", for ease of grep/dxr/searchfox. But if you're already committed upstream, that's OK.
Attachment #8875502 -
Flags: review?(nalexander) → review+
Pushed by gkruglov@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a43b9bebbc13 Add switchboard experiment for background telemetry processing r=nalexander
Comment 8•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a43b9bebbc13
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•