[DoH] Heuristics telemetry event is using max allowed extra key count
Categories
(Firefox :: Security, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox80 | --- | fixed |
People
(Reporter: nhnt11, Assigned: nhnt11)
References
Details
Attachments
(1 file, 1 obsolete file)
We currently have 10 extra keys on the telemetry event, which is the limit. This prevents us from easily adding a new heuristic or a network ID key.
We need to capture these results in a more sustainable way. I can see a few options:
- Set up boolean histograms for each heuristic.
- Send a separate event for each heuristic.
- Use scalar counts to track only disable_doh results for each heuristic.
My order of preference would be 3 > 1 > 2. It depends on what questions we want to answer. So far, we've been looking at overall rate of enabling/disabling doh, and comparing the individual heuristic trip-rates with each other. This makes me think option 3) should suffice.
Tim, Dragana, Nhi, do you have any thoughts on this?
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
•
|
||
Uh, actually, I think a categorical histogram is what I want.
Assignee | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
Option 4 is a more compact event serialization, which it looks like we're rolling with. :) I wave my data steward hands at this and assert that it's isomorphic to the existing collection and the prior approval in bug 1553700 applies.
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Description
•