Record details about success/failure to fetch the blocklist

NEW
Unassigned

Status

Firefox Health Report
Client: Desktop
P4
enhancement
4 years ago
3 years ago

People

(Reporter: Benjamin Smedberg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [measurement:client])

(Reporter)

Description

4 years ago
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

4 years ago
Points: --- → 8
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.
Flags: needinfo?(dtownsend+bugmail)
Flags: needinfo?(dtownsend+bugmail)
Priority: -- → P4
Whiteboard: [measurement:client]
You need to log in before you can comment on or make changes to this bug.