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.
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.
Priority: -- → P4
You need to log in before you can comment on or make changes to this bug.