Add telemetry to record per download result in download protection

RESOLVED FIXED in Firefox 65

Status

()

enhancement
P2
normal
RESOLVED FIXED
7 months ago
6 months ago

People

(Reporter: dimi, Assigned: dimi)

Tracking

(Blocks 1 bug)

unspecified
mozilla65
Points:
---

Firefox Tracking Flags

(firefox65 fixed)

Details

Attachments

(3 attachments, 1 obsolete attachment)

(Assignee)

Description

7 months ago
We need a per download result in download protection to help us know what could we improve next. It will be also useful to see if there is anything unusual.

For example, by retrieving the information, we could understand the priority of Bug 1356426 better (See Bug 1356246 Comment 2).
(Assignee)

Updated

7 months ago
Priority: -- → P2
(Assignee)

Comment 1

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

Updated

7 months ago
Attachment #9019033 - Attachment is obsolete: true
(Assignee)

Comment 2

7 months ago
In this patch, we added a telemetry to record different reasons that
why download protection service decides to allow or block this download.

The |verdict| and |shouldBlock| parameters are moved inside
PendingLookup::OnComplete and now we used |Reason| in the query
reputation code path instead

Use enumerated Telemetry because it is easier to add more reasons in the
future.
(Assignee)

Comment 3

7 months ago
Add "Reason" checks in the testcase because it provides more
fine-grained check.

In this patch, I also refactor the testcase by move telemetry stuff
into head_download_manager.js so it could easily used by different testcases.
(Assignee)

Comment 4

6 months ago
(Assignee)

Updated

6 months ago
Attachment #9024419 - Flags: review?(francois)
Comment on attachment 9024419 [details]
request-bug-1500360.txt

> 8) If this data collection is default on, what is the opt-out mechanism for users?
> I'm not aware of what the opt-out mechanisms are for data collection in Firefox

Users can turn off telemetry.
Comment on attachment 9024419 [details]
request-bug-1500360.txt

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

Yes, in Histograms.json.

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

Yes, telemetry setting.

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

Yes, Dimi Lee.

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?  **

Category 1.

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

Default ON.

6) Does the instrumentation include the addition of **any *new* identifiers** (whether anonymous or otherwise; e.g., username, random IDs, etc.  See the appendix for more details)?

No.

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

Yes.

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

No, permanent.
Attachment #9024419 - Flags: review?(francois) → review+

Comment 7

6 months ago
Pushed by dlee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/db270ae8003b
P1. Add telemetry to record the reason download protection allow or block the download. r=francois
https://hg.mozilla.org/integration/autoland/rev/dc40390fd436
P2. Use reason in download protection testcases. r=francois

Comment 8

6 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/db270ae8003b
https://hg.mozilla.org/mozilla-central/rev/dc40390fd436
Status: ASSIGNED → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in before you can comment on or make changes to this bug.