Add telemetry on Network Settings UI interaction
Categories
(Core :: Networking, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: kershaw, Assigned: omansfeld)
Details
(Whiteboard: [necko-triaged] [necko-priority-queue])
Attachments
(1 file)
We aim to gain insights into how users interact with the network settings page. Specifically, we want to understand how proxies are configured, whether through proxy auto-config, enterprise policies, add-ons, or manual settings adjustments.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Am I correct to assume that those are the settings that are to be monitored?
enum {
PROXYCONFIG_DIRECT = 0U,
PROXYCONFIG_MANUAL = 1U,
PROXYCONFIG_PAC = 2U,
PROXYCONFIG_WPAD = 4U,
PROXYCONFIG_SYSTEM = 5U
};
I already started working on a patch for collecting them and just wanted to double check.
| Assignee | ||
Comment 2•1 year ago
|
||
| Reporter | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Not sure if event telemetry was the most appropriate kind of telemetry - looker only lets me run queries that process less than 10Tb of data 🙂
In any case, here's a query for the past 3 days:
https://mozilla.cloud.looker.com/x/Lar8VMIseVh9MhuH5mFev9
| row | date | key | event count | client count |
1 2025-02-12 PAC 3,075 1,760
2 2025-02-12 MANUAL 65,439 20,255
3 2025-02-12 DIRECT 24,425 14,797
4 2025-02-12 WPAD 4,483 3,185
5 2025-02-12 SYSTEM 11,535 7,708
6 2025-02-11 PAC 2,890 1,685
7 2025-02-11 MANUAL 66,483 20,175
8 2025-02-11 DIRECT 23,294 14,113
9 2025-02-11 WPAD 4,309 3,119
10 2025-02-11 SYSTEM 11,445 7,398
Description
•