Closed
Bug 1057414
Opened 10 years ago
Closed 6 years ago
Record details about success/failure to fetch the blocklist
Categories
(Firefox Health Report Graveyard :: Client: Desktop, enhancement, P4)
Firefox Health Report Graveyard
Client: Desktop
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: benjamin, Unassigned)
Details
(Whiteboard: [measurement:client])
We currently record the blocklist activation state in the FHR payload. In order to understand whether the blocklist is effective for a given user, we should also record success or failure to fetch the blocklist. Success can be a simple count, but failure should probably be a slightly more detailed log entry indicating the reason (timeout/certificate/etc). This is currently not a high-priority work item.
Reporter | ||
Updated•10 years ago
|
Points: --- → 8
Comment 1•10 years ago
|
||
Given that ~1% of FHR users have the blocklist disabled, and there's anecdotal examples of misbehaving add-ons blocking updates for Firefox and Chrome users, I'd like to know if the service is working as expected, or if we're seeing interference from malicious apps/add-ons. I talked with Dave about this a little while ago, he may have cycles to make this happen quicker.
Updated•10 years ago
|
Flags: needinfo?(dtownsend+bugmail)
Updated•10 years ago
|
Flags: needinfo?(dtownsend+bugmail)
Updated•8 years ago
|
Priority: -- → P4
Whiteboard: [measurement:client]
Comment 2•6 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=1497137; component has been deprecated.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Updated•6 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•