Closed Bug 1411266 Opened 7 years ago Closed 7 years ago

Research telemetry states for Linux builds

Categories

(Toolkit :: Telemetry, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
Tracking Status
firefox57 --- unaffected
firefox58 --- affected

People

(Reporter: Dexter, Assigned: Dexter)

References

(Blocks 1 open bug)

Details

We need to check what's the state of the telemetry flags on the Linux distributions we know are sending Telemetry:

- "toolkit.telemetry.enabled" default value;
- MOZILLA_OFFICIAL status;
- what channel names are being used;
- if they provide different defaults and enable extended telemetry by default.
Assignee: nobody → alessio.placitelli
Blocks: 1406390
Priority: -- → P1
Blocks: 1411269
By doing some nice code archaeology on the dependencies of bug 1233687, I found that:

- MOZILLA_OFFICIAL is defined (as expected);
- "toolkit.telemetry.enabled" is false on Release (as expected);
- By looking at https://sql.telemetry.mozilla.org/queries/47690 we can see that a few builds are sending Telemetry on the "default" channel. Fedora seems to be the biggest one.
Is toolkit.telemetry.enabled false on non-release as well? Could it be that we currently just do not receive extended data from  any channel on Linux repacks?
(In reply to Chris H-C :chutten from comment #2)
> Is toolkit.telemetry.enabled false on non-release as well? Could it be that
> we currently just do not receive extended data from  any channel on Linux
> repacks?

I just checked the repacked Nightly on Ubuntu and toolkit.telemetry.enabled defaults to true, so it follows our behaviour. I'll check Fedora as well.
How do they disable t.t.e then... do they use the app.update.channel of "release"
(In reply to Chris H-C :chutten from comment #4)
> How do they disable t.t.e then... do they use the app.update.channel of
> "release"

Yes, Ubuntu Firefox does that.
A volunteer helped verifying Firefox on Fedora. The prefs behave as expected and as outlined in comment 6.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.