Add telemetry to know the remote lookup result for archive files

RESOLVED FIXED in Firefox 66

Status

()

enhancement
P2
normal
RESOLVED FIXED
7 months ago
4 months ago

People

(Reporter: dimi, Assigned: dimi)

Tracking

(Blocks 1 bug)

unspecified
mozilla66
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox66 fixed)

Details

Attachments

(2 attachments, 1 obsolete attachment)

Assignee

Description

7 months ago
This could help us know the improvement after including archived files information in the remote lookup request.
I think this is important because we can reference the result here to guess the potential gain if we want to implement dmg/RAR extraction.


This should land earlier so we can get the result "before" having zip extraction feature.
Assignee

Comment 1

7 months ago
The idea I have in mind is not limit the telemetry just for archived files. Maybe a telemetry with file extension as the key is more flexible and general.
Priority: -- → P3
Assignee

Comment 2

7 months ago
Posted patch WIP Patch (obsolete) — Splinter Review
Assignee

Comment 3

6 months ago
Add APPLICATION_REPUTATION_SERVER_VERDICT_2 telemetry with file extension as the key.
This can give us an idea about the current detecion rate for archived
files.
Assignee

Updated

6 months ago
Priority: P3 → P2
Assignee

Comment 4

4 months ago
Attachment #9024585 - Attachment is obsolete: true
Assignee

Updated

4 months ago
Attachment #9036852 - Flags: review?(chutten)

Comment 5

4 months ago

Comment on attachment 9036852 [details]
data-review-request.txt

Preliminary note:

From your comments about the questions being answered and the analysis you plan on performing, it seems to me that this measurement might serve its purposes if it expired in, say, Firefox 71 instead of being permanent. If so, it would be serving the principles of Lean Data to do so. (and we could always renew it if it then proves useful to have on an ongoing basis).

To be clear it passes Data Collection Review whether it expires or is permanent.

Speaking of which, for permanent collections it is wise to have them covered by an automated test ensuring that your collection doesn't break in the future. (without the expiry/renewal cycle ensuring we take a look at them every so often, collections can break without notice unless covered by tests).

DATA COLLECTION REVIEW RESPONSE:

Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes. This collection is Telemetry so is documented in its definitions file (Histograms.json), the Probe Dictionary, and on telemetry.mozilla.org's Measurement Dashboards.

Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

If the request is for permanent data collection, is there someone who will monitor the data over time?

Yes. Dimi Lee is responsible.

Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, Interaction. (Though the result of the reputation request is Category 1, the reputation requests map 1:1 onto user interactions.)

Is the data collection request for default-on or default-off?

Default on, all channels.

Does the instrumentation include the addition of any new identifiers?

No. It does add a string key but the key must be a member of a build-time list. The key is of limited domain and doesn't fit the definition of "identifier"

Is the data collection covered by the existing Firefox privacy notice?

Yes.

Does there need to be a check-in in the future to determine whether to renew the data?

No. This collection is permanent.


Result: datareview+

Attachment #9036852 - Flags: review?(chutten) → review+
Assignee

Comment 6

4 months ago

(In reply to Chris H-C :chutten from comment #5)

Comment on attachment 9036852 [details]
data-review-request.txt

Preliminary note:

From your comments about the questions being answered and the analysis you plan on performing, it seems to me that this measurement might serve its purposes if it expired in, say, Firefox 71 instead of being permanent. If so, it would be serving the principles of Lean Data to do so. (and we could always renew it if it then proves useful to have on an ongoing basis).

To be clear it passes Data Collection Review whether it expires or is permanent.

Speaking of which, for permanent collections it is wise to have them covered by an automated test ensuring that your collection doesn't break in the future. (without the expiry/renewal cycle ensuring we take a look at them every so often, collections can break without notice unless covered by tests).

Thank you for your suggestion, I'll change it to expired in Firefox 71 :)

Comment 7

4 months ago
Pushed by dlee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f412108e7d77
Add keyed telemetry to know the download protection remote lookup result . r=francois

Comment 8

4 months ago
bugherder
Status: ASSIGNED → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
You need to log in before you can comment on or make changes to this bug.